From: Yisheng Xie <xieyisheng1@huawei.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: <linux-kernel@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<ysxie@foxmail.com>, Wim Van Sebroeck <wim@iguana.be>,
<linux-watchdog@vger.kernel.org>
Subject: Re: [v3,21/27] watchdog: replace devm_ioremap_nocache with devm_ioremap
Date: Wed, 27 Dec 2017 17:36:01 +0800 [thread overview]
Message-ID: <30d0f7f4-8f93-de23-83b7-72a9c8d4a47f@huawei.com> (raw)
In-Reply-To: <20171226172831.GA23118@roeck-us.net>
Hi Guenter,
On 2017/12/27 1:28, Guenter Roeck wrote:
> On Sat, Dec 23, 2017 at 07:01:37PM +0800, Yisheng Xie 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.
>> >
> I don't have issues with the patch itself - on mips, the definitions
> _are_ the same - but with the description. It is not universally correct
> that the definitions are the same. Please update and resubmit.
>
Right, there are 4 archs have different meaning of ioremap. And presently, I
still do not know why.
For this patch itself, maybe I can update and resubmit.
Thanks and Merry Christmas.
Yisheng
> Guenter
>
prev parent reply other threads:[~2017-12-27 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 11:01 [PATCH v3 21/27] " Yisheng Xie
2017-12-26 17:28 ` [v3,21/27] " Guenter Roeck
2017-12-27 9:36 ` 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=30d0f7f4-8f93-de23-83b7-72a9c8d4a47f@huawei.com \
--to=xieyisheng1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
--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®