From: Johan Hovold <johan@kernel.org>
To: Jingjing Liu <liujingjing@cdjrlc.com>
Cc: gerg@linux-m68k.org, geert@linux-m68k.org,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: coldfire: Prefer unsigned int to bare use of unsigned
Date: Wed, 3 Nov 2021 09:02:52 +0100 [thread overview]
Message-ID: <YYJCLKm1xVppeUV/@hovoldconsulting.com> (raw)
In-Reply-To: <20211103072252.24556-1-liujingjing@cdjrlc.com>
On Wed, Nov 03, 2021 at 03:22:52PM +0800, Jingjing Liu wrote:
> Fix checkpatch warnings:
> WARNING: Prefer 'unsigned int' to bare use of 'unsigned'
>
> Signed-off-by: Jingjing Liu <liujingjing@cdjrlc.com>
As I just wrote elsewhere:
Please don't run checkpatch.pl on code that's already in the kernel. Use
it to check your own patches before submitting them.
If you want to practise the patch submission process you can do so in
drivers/staging/ where "clean ups" such as this one are currently
accepted.
Johan
prev parent reply other threads:[~2021-11-03 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 7:22 [PATCH] m68k: coldfire: Prefer unsigned int to bare use of unsigned Jingjing Liu
2021-11-03 8:02 ` Johan Hovold [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=YYJCLKm1xVppeUV/@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=liujingjing@cdjrlc.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