From: xuanzhenggang001@208suo.com
To: richard.henderson@linaro.org, ink@jurassic.park.msu.ru
Cc: mattst88@gmail.com, viro@zeniv.linux.org.uk,
linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] alpha/boot/misc: prefer 'unsigned int' to bare use of 'unsigned'
Date: Sun, 09 Jul 2023 22:12:06 +0800 [thread overview]
Message-ID: <60256ab738fe281c1fb3ec72fba62c60@208suo.com> (raw)
In-Reply-To: <20230709141002.8229-1-denghuilong@cdjrlc.com>
Fix the following warnings reported by checkpatch:
arch/alpha/boot/misc.c:48: WARNING: Prefer 'unsigned int' to bare use of
'unsigned'
arch/alpha/boot/misc.c:49: WARNING: Prefer 'unsigned int' to bare use of
'unsigned'
arch/alpha/boot/misc.c:50: WARNING: Prefer 'unsigned int' to bare use of
'unsigned'
arch/alpha/boot/misc.c:124: WARNING: Prefer 'unsigned int' to bare use
of 'unsigned'
Signed-off-by: Zhenggang Xuan <xuanzhenggang001@208suo.com>
---
arch/alpha/boot/misc.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/alpha/boot/misc.c b/arch/alpha/boot/misc.c
index 1ab91852d9f7..7d3249972587 100644
--- a/arch/alpha/boot/misc.c
+++ b/arch/alpha/boot/misc.c
@@ -45,9 +45,9 @@ typedef unsigned long ulg;
static uch *inbuf; /* input buffer */
static uch *window; /* Sliding window buffer */
-static unsigned insize; /* valid bytes in inbuf */
-static unsigned inptr; /* index of next byte to be processed in
inbuf */
-static unsigned outcnt; /* bytes in output buffer */
+static unsigned int insize; /* valid bytes in inbuf */
+static unsigned int inptr; /* index of next byte to be processed
in inbuf */
+static unsigned int outcnt; /* bytes in output buffer */
/* gzip flag byte */
#define ASCII_FLAG 0x01 /* bit 0 set: file probably ascii text */
@@ -121,7 +121,7 @@ int fill_inbuf(void)
void flush_window(void)
{
ulg c = crc;
- unsigned n;
+ unsigned int n;
uch *in, *out, ch;
in = window;
parent reply other threads:[~2023-07-09 14:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230709141002.8229-1-denghuilong@cdjrlc.com>]
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=60256ab738fe281c1fb3ec72fba62c60@208suo.com \
--to=xuanzhenggang001@208suo.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).