From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: linux-watchdog@vger.kernel.org
Cc: wim@linux-watchdog.org, linux@roeck-us.net, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] watchdog: rt2880-wdt: prefer unsigned int over unsigned
Date: Wed, 1 Mar 2023 07:55:10 +0100 [thread overview]
Message-ID: <20230301065510.2818425-2-sergio.paracuellos@gmail.com> (raw)
In-Reply-To: <20230301065510.2818425-1-sergio.paracuellos@gmail.com>
Instead of declare 'reg' variable in read and write operations as a bare
'unsigned' type prefer to declate it as 'unsigned int'.
Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
---
drivers/watchdog/rt2880_wdt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/watchdog/rt2880_wdt.c b/drivers/watchdog/rt2880_wdt.c
index e54737bcf939..4499ba0eb5ea 100644
--- a/drivers/watchdog/rt2880_wdt.c
+++ b/drivers/watchdog/rt2880_wdt.c
@@ -54,12 +54,12 @@ MODULE_PARM_DESC(nowayout,
"Watchdog cannot be stopped once started (default="
__MODULE_STRING(WATCHDOG_NOWAYOUT) ")");
-static inline void rt_wdt_w32(void __iomem *base, unsigned reg, u32 val)
+static inline void rt_wdt_w32(void __iomem *base, unsigned int reg, u32 val)
{
iowrite32(val, base + reg);
}
-static inline u32 rt_wdt_r32(void __iomem *base, unsigned reg)
+static inline u32 rt_wdt_r32(void __iomem *base, unsigned int reg)
{
return ioread32(base + reg);
}
--
2.25.1
next prev parent reply other threads:[~2023-03-01 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 6:55 [PATCH 1/2] watchdog: rt2880-wdt: avoid static global declarations Sergio Paracuellos
2023-03-01 6:55 ` Sergio Paracuellos [this message]
2023-03-07 17:46 ` [PATCH 2/2] watchdog: rt2880-wdt: prefer unsigned int over unsigned Guenter Roeck
2023-03-07 17:46 ` [PATCH 1/2] watchdog: rt2880-wdt: avoid static global declarations Guenter Roeck
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=20230301065510.2818425-2-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
/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).