From: Jakub Kicinski <kuba@kernel.org>
To: Li zeming <zeming@nfschina.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/socket: Remove unnecessary ‘0’ values from used
Date: Fri, 1 Sep 2023 17:57:14 -0700 [thread overview]
Message-ID: <20230901175714.1f2826bb@kernel.org> (raw)
In-Reply-To: <20230902182228.3124-1-zeming@nfschina.com>
On Sun, 3 Sep 2023 02:22:28 +0800 Li zeming wrote:
> used is assigned first, so it does not need to initialize the
> assignment.
It's a perfectly legitimate code pattern.
Please do not post any such patches to networking.
Please make sure you have read this:
https://docs.kernel.org/process/researcher-guidelines.html
--
pw-bot: reject
prev parent reply other threads:[~2023-09-02 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 18:22 [PATCH] net/socket: Remove unnecessary ‘0’ values from used Li zeming
2023-09-01 11:07 ` Denis Kirjanov
2023-09-02 0:57 ` Jakub Kicinski [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=20230901175714.1f2826bb@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zeming@nfschina.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).