From: Linus Walleij <linus.walleij@linaro.org>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
ysxie@foxmail.com, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 06/27] gpio: replace devm_ioremap_nocache with devm_ioremap
Date: Wed, 3 Jan 2018 08:48:52 +0100 [thread overview]
Message-ID: <CACRpkdayoOOswWyi_1iBD4zpo99YZh_mPF_dYCvZbfSyv9hi5A@mail.gmail.com> (raw)
In-Reply-To: <ca2bf6e4-096a-92f7-923d-3e5f72167fa1@huawei.com>
On Wed, Jan 3, 2018 at 7:05 AM, Yisheng Xie <xieyisheng1@huawei.com> wrote:
> On 2018/1/2 16:41, Linus Walleij wrote:
>> On Sat, Dec 23, 2017 at 11:58 AM, Yisheng Xie <xieyisheng1@huawei.com> wrote:
>>
>>> Default ioremap is ioremap_nocache, so devm_ioremap has the same
>>> function with devm_ioremap_nocache, which can just be killed to
>>> save the size of devres.o
>>>
>>> This patch is to use use devm_ioremap instead of devm_ioremap_nocache,
>>> which should not have any function change but prepare for killing
>>> devm_ioremap_nocache.
>>>
>>> Cc: Linus Walleij <linus.walleij@linaro.org>
>>> Cc: linux-gpio@vger.kernel.org
>>> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
>
> Well, I list the ARCHs related to the change file, do not include cris,ia64,mn10300
> and openrisc, which ioremap is not the same as ioremap_nocache, as discussed in cover
> letter. So please let me know if I need update the comment.
I dropped the patch until it's figured out that none of these arches
are affected
by the change.
Please resend with a comment explaining why the change is harmless on the
architectures these drivers are for.
Yours,
Linus Walleij
prev parent reply other threads:[~2018-01-03 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 10:58 [PATCH v3 06/27] gpio: replace devm_ioremap_nocache with devm_ioremap Yisheng Xie
2018-01-02 8:41 ` Linus Walleij
2018-01-03 6:05 ` Yisheng Xie
2018-01-03 7:48 ` Linus Walleij [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=CACRpkdayoOOswWyi_1iBD4zpo99YZh_mPF_dYCvZbfSyv9hi5A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xieyisheng1@huawei.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;
as well as URLs for NNTP newsgroup(s).