From: Stephen Hemminger <stephen@networkplumber.org>
To: hanyu001@208suo.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH] 3c574_cs: Prefer unsigned int to bare use of unsigned
Date: Mon, 17 Jul 2023 08:05:02 -0700 [thread overview]
Message-ID: <20230717080502.21b6b1f5@hermes.local> (raw)
In-Reply-To: <7f6fba66a5cad4486c04efe56ded5ae9@208suo.com>
On Mon, 17 Jul 2023 11:11:11 +0800
hanyu001@208suo.com wrote:
> This patch fixes the checkpatch.pl error
>
> ./drivers/net/ethernet/3com/3c574_cs.c:770: WARNING: Prefer 'unsigned
> int' to bare use of 'unsigned'
>
> Signed-off-by: maqimei <2433033762@qq.com>
Patches that just derived from checkpatch fixes are not accepted in netdev.
Didn't you already hear that from the maintainers.
Repeating with more patches will just get you blacklisted.
prev parent reply other threads:[~2023-07-17 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_C283203D2CCA281A87720665D83277B4CE0A@qq.com>
2023-07-17 3:11 ` [PATCH] 3c574_cs: Prefer unsigned int to bare use of unsigned hanyu001
2023-07-17 15:05 ` Stephen Hemminger [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=20230717080502.21b6b1f5@hermes.local \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hanyu001@208suo.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).