From: Yisheng Xie <xieyisheng1@huawei.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mips@linux-mips.org>,
<ulf.hansson@linaro.org>, <jakub.kicinski@netronome.com>,
<airlied@linux.ie>, <linux-wireless@vger.kernel.org>,
<linus.walleij@linaro.org>, <alsa-devel@alsa-project.org>,
<dri-devel@lists.freedesktop.org>,
<platform-driver-x86@vger.kernel.org>,
<linux-ide@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
<daniel.vetter@intel.com>, <dan.j.williams@intel.com>,
<jason@lakedaemon.net>, <linux-rtc@vger.kernel.org>,
<boris.brezillon@free-electrons.com>, <mchehab@kernel.org>,
<dmaengine@vger.kernel.org>, <vinod.koul@intel.com>,
<richard@nod.at>, <marek.vasut@gmail.com>,
<industrypack-devel@lists.sourceforge.net>,
<linux-pci@vger.kernel.org>, <dvhart@infradead.org>,
<linux@roeck-us.net>, <linux-media@vger.kernel.org>,
<seanpaul@chromium.org>, <devel@driverdev.osuosl.org>,
<linux-watchdog@vger.kernel.org>, <arnd@arndb.de>,
<b.zolnierkie@samsung.com>, <marc.zyngier@arm.com>,
<jslaby@suse.com>, <jani.nikula@linux.intel.com>,
<linux-can@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<broonie@kernel.org>, <mkl@pengutronix.de>,
<linux-fbdev@vger.kernel.org>, <nios2-dev@lists.rocketboards.org>,
<bhelgaas@google.com>, <tglx@linutronix.de>,
<andriy.shevchenko@linux.intel.com>, <kvalo@codeaurora.org>,
<a.zummo@towertech.it>, <netdev@vger.kernel.org>,
<linux-mmc@vger.kernel.org>, <lgirdwood@gmail.com>,
<ralf@linux-mips.org>, <linux-spi@vger.kernel.org>,
<ysxie@foxmail.com>, <wg@grandegger.com>,
<cyrille.pitchen@wedev4u.fr>, <tj@kernel.org>,
<alexandre.belloni@free-electrons.com>, <davem@davemloft.net>,
<andy@infradead.org>
Subject: Re: [PATCH v3 27/27] devres: kill devm_ioremap_nocache
Date: Mon, 25 Dec 2017 09:43:40 +0800 [thread overview]
Message-ID: <4d0991ec-9cd4-0c33-5560-ae9c2c762765@huawei.com> (raw)
In-Reply-To: <20171223134532.GA10103@kroah.com>
On 2017/12/23 21:45, Greg KH wrote:
> On Sat, Dec 23, 2017 at 07:02:59PM +0800, Yisheng Xie wrote:
>> --- a/lib/devres.c
>> +++ b/lib/devres.c
>> @@ -44,35 +44,6 @@ void __iomem *devm_ioremap(struct device *dev, resource_size_t offset,
>> EXPORT_SYMBOL(devm_ioremap);
>>
>> /**
>> - * devm_ioremap_nocache - Managed ioremap_nocache()
>> - * @dev: Generic device to remap IO address for
>> - * @offset: Resource address to map
>> - * @size: Size of map
>> - *
>> - * Managed ioremap_nocache(). Map is automatically unmapped on driver
>> - * detach.
>> - */
>> -void __iomem *devm_ioremap_nocache(struct device *dev, resource_size_t offset,
>> - resource_size_t size)
>> -{
>> - void __iomem **ptr, *addr;
>> -
>> - ptr = devres_alloc(devm_ioremap_release, sizeof(*ptr), GFP_KERNEL);
>> - if (!ptr)
>> - return NULL;
>> -
>> - addr = ioremap_nocache(offset, size);
>
> Wait, devm_ioremap() calls ioremap(), not ioremap_nocache(), are you
> _SURE_ that these are all identical? For all arches? If so, then
> ioremap_nocache() can also be removed, right?
Yeah, As Christophe pointed out, that 4 archs do not have the same function.
But I do not why they do not want do the same thing. Driver may no know about
this? right?
>
> In my quick glance, I don't think you can do this series at all :(
Yes, maybe should take Christophe suggestion and use a bool or enum to distinguish them?
Thanks
Yisheng
>
> greg k-h
>
> .
>
prev parent reply other threads:[~2017-12-25 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 11:02 Yisheng Xie
2017-12-23 13:45 ` Greg KH
2017-12-25 1:43 ` Yisheng Xie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d0991ec-9cd4-0c33-5560-ae9c2c762765@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=a.zummo@towertech.it \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@free-electrons.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy@infradead.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=bhelgaas@google.com \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dan.j.williams@intel.com \
--cc=daniel.vetter@intel.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=industrypack-devel@lists.sourceforge.net \
--cc=jakub.kicinski@netronome.com \
--cc=jani.nikula@linux.intel.com \
--cc=jason@lakedaemon.net \
--cc=jslaby@suse.com \
--cc=kvalo@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marc.zyngier@arm.com \
--cc=marek.vasut@gmail.com \
--cc=mchehab@kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=nios2-dev@lists.rocketboards.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
--cc=seanpaul@chromium.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vinod.koul@intel.com \
--cc=wg@grandegger.com \
--cc=ysxie@foxmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®