From: Guenter Roeck <linux@roeck-us.net>
To: Yisheng Xie <xieyisheng1@huawei.com>
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: Tue, 26 Dec 2017 09:28:31 -0800 [thread overview]
Message-ID: <20171226172831.GA23118@roeck-us.net> (raw)
In-Reply-To: <1514026897-33581-1-git-send-email-xieyisheng1@huawei.com>
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.
Guenter
> Cc: Wim Van Sebroeck <wim@iguana.be>
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: linux-watchdog@vger.kernel.org
> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
> ---
> drivers/watchdog/bcm63xx_wdt.c | 4 ++--
> drivers/watchdog/rc32434_wdt.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/watchdog/bcm63xx_wdt.c b/drivers/watchdog/bcm63xx_wdt.c
> index 8555afc..697a7e7 100644
> --- a/drivers/watchdog/bcm63xx_wdt.c
> +++ b/drivers/watchdog/bcm63xx_wdt.c
> @@ -248,8 +248,8 @@ static int bcm63xx_wdt_probe(struct platform_device *pdev)
> return -ENODEV;
> }
>
> - bcm63xx_wdt_device.regs = devm_ioremap_nocache(&pdev->dev, r->start,
> - resource_size(r));
> + bcm63xx_wdt_device.regs = devm_ioremap(&pdev->dev, r->start,
> + resource_size(r));
> if (!bcm63xx_wdt_device.regs) {
> dev_err(&pdev->dev, "failed to remap I/O resources\n");
> return -ENXIO;
> diff --git a/drivers/watchdog/rc32434_wdt.c b/drivers/watchdog/rc32434_wdt.c
> index 3a75f3b..7d519c5 100644
> --- a/drivers/watchdog/rc32434_wdt.c
> +++ b/drivers/watchdog/rc32434_wdt.c
> @@ -31,7 +31,7 @@
> #include <linux/platform_device.h> /* For platform_driver framework */
> #include <linux/spinlock.h> /* For spin_lock/spin_unlock/... */
> #include <linux/uaccess.h> /* For copy_to_user/put_user/... */
> -#include <linux/io.h> /* For devm_ioremap_nocache */
> +#include <linux/io.h> /* For devm_ioremap */
>
> #include <asm/mach-rc32434/integ.h> /* For the Watchdog registers */
>
> @@ -271,7 +271,7 @@ static int rc32434_wdt_probe(struct platform_device *pdev)
> return -ENODEV;
> }
>
> - wdt_reg = devm_ioremap_nocache(&pdev->dev, r->start, resource_size(r));
> + wdt_reg = devm_ioremap(&pdev->dev, r->start, resource_size(r));
> if (!wdt_reg) {
> pr_err("failed to remap I/O resources\n");
> return -ENXIO;
next prev parent reply other threads:[~2017-12-26 17:28 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 ` Guenter Roeck [this message]
2017-12-27 9:36 ` [v3,21/27] " Yisheng Xie
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=20171226172831.GA23118@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
--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
all inboxes | Powered by JetHome®