From: Simon Horman <horms@kernel.org>
To: George Guo <dongtai.guo@linux.dev>
Cc: pabeni@redhat.com, davem@davemloft.net, edumazet@google.com,
guodongtai@kylinos.cn, kuba@kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
paul@paul-moore.com
Subject: Re: [PATCH 1/1] add comment for doi_remove in struct netlbl_lsm_secattr
Date: Fri, 25 Oct 2024 14:40:28 +0100 [thread overview]
Message-ID: <20241025134028.GW1202098@kernel.org> (raw)
In-Reply-To: <20241025064031.994215-1-dongtai.guo@linux.dev>
On Fri, Oct 25, 2024 at 02:40:31PM +0800, George Guo wrote:
> From: George Guo <guodongtai@kylinos.cn>
Hi George,
Thanks for your patch. I agree that is is correct and a good change
to make. But there are some process issues to be addressed before this
patch can be accepted.
Firstly, as this is presumably a non-bug fix for networking code,
it should be targeted at the net-next tree. That it should
be based on that tree (it seems to be) and explicitly targeted
at that tree in the Subject.
Subject: [PATCH net-next v2] ...
Secondly, the subject should include a prefix.
Looking at git log include/net/netlabel.h it
seems that should be 'netlabel:'
Subject: [PATCH net-next v2] netlabel: ...
And it might be best to make the subject a bit more descriptive.
Subject: [PATCH net-next v2] netlabel: document doi_remove field of struct netlbl_calipso_ops
Next, a commit message is required. It should explain why the change is
being made. And, ideally how you found this problem. It should
also include a Signed-off-by line [1]. e.g.
Add documentation of do_remove field to Kernel doc for struct
netlbl_calipso_ops.
Found using W=1 build.
Signed-off-by: ...
[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
Lastly, please do wait 24h before posting a new version.
Please include information about what has changed below the scissors ('---').
And please send the new patch as a new thread.
More information on development processes for Networking can be found here:
https://docs.kernel.org/process/maintainer-netdev.html
...
--
pw-bot: changes-requested
next prev parent reply other threads:[~2024-10-25 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 8:07 [PATCH 1/1] netlabel: Add missing comment to struct field George Guo
2024-09-23 11:52 ` Paul Moore
2024-09-24 10:43 ` Paolo Abeni
2024-10-25 6:40 ` [PATCH 1/1] add comment for doi_remove in struct netlbl_lsm_secattr George Guo
2024-10-25 13:40 ` Simon Horman [this message]
2024-10-25 6:54 ` George Guo
2024-10-25 13:50 ` Simon Horman
2024-10-25 7:02 ` [PATCH 1/1] netlabel: Add missing comment to struct field George Guo
2024-10-25 13:53 ` Simon Horman
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=20241025134028.GW1202098@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=dongtai.guo@linux.dev \
--cc=edumazet@google.com \
--cc=guodongtai@kylinos.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.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).