From: xuanzhenggang001@208suo.com
To: tony@atomide.com
Cc: linux@armlinux.org.uk, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] ARM: OMAP2+: prefer 'unsigned int' to bare use of 'unsigned'
Date: Sun, 09 Jul 2023 21:59:41 +0800 [thread overview]
Message-ID: <7efba6a4aae52649aa05756263c0a955@208suo.com> (raw)
In-Reply-To: <20230709135705.59832-1-denghuilong@cdjrlc.com>
arch/arm/mach-omap2/display.c:73: WARNING: Prefer 'unsigned int' to bare
use of 'unsigned'
arch/arm/mach-omap2/display.c:111: WARNING: Prefer 'unsigned int' to
bare use of 'unsigned'
arch/arm/mach-omap2/display.c:119: WARNING: Prefer 'unsigned int' to
bare use of 'unsigned'
Signed-off-by: Zhenggang Xuan <xuanzhenggang001@208suo.com>
---
arch/arm/mach-omap2/display.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/display.c
b/arch/arm/mach-omap2/display.c
index dbec3bb9fbf4..c7a39d497e47 100644
--- a/arch/arm/mach-omap2/display.c
+++ b/arch/arm/mach-omap2/display.c
@@ -70,7 +70,7 @@ static struct platform_device omap_display_device = {
static struct regmap *omap4_dsi_mux_syscon;
-static int omap4_dsi_mux_pads(int dsi_id, unsigned lanes)
+static int omap4_dsi_mux_pads(int dsi_id, unsigned int lanes)
{
u32 enable_mask, enable_shift;
u32 pipd_mask, pipd_shift;
@@ -108,7 +108,7 @@ static int omap4_dsi_mux_pads(int dsi_id, unsigned
lanes)
return 0;
}
-static int omap_dsi_enable_pads(int dsi_id, unsigned lane_mask)
+static int omap_dsi_enable_pads(int dsi_id, unsigned int lane_mask)
{
if (cpu_is_omap44xx())
return omap4_dsi_mux_pads(dsi_id, lane_mask);
@@ -116,7 +116,7 @@ static int omap_dsi_enable_pads(int dsi_id, unsigned
lane_mask)
return 0;
}
-static void omap_dsi_disable_pads(int dsi_id, unsigned lane_mask)
+static void omap_dsi_disable_pads(int dsi_id, unsigned int lane_mask)
{
if (cpu_is_omap44xx())
omap4_dsi_mux_pads(dsi_id, 0);
next parent reply other threads:[~2023-07-09 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230709135705.59832-1-denghuilong@cdjrlc.com>
2023-07-09 13:59 ` xuanzhenggang001 [this message]
2023-07-31 6:43 ` Tony Lindgren
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=7efba6a4aae52649aa05756263c0a955@208suo.com \
--to=xuanzhenggang001@208suo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tony@atomide.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®