From: Paolo Abeni <pabeni@redhat.com>
To: George Guo <dongtai.guo@linux.dev>,
paul@paul-moore.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, George Guo <guodongtai@kylinos.cn>
Subject: Re: [PATCH 1/1] netlabel: Add missing comment to struct field
Date: Tue, 24 Sep 2024 12:43:30 +0200 [thread overview]
Message-ID: <0667f18b-2228-4201-9da7-0e3536bae321@redhat.com> (raw)
In-Reply-To: <20240923080733.2914087-1-dongtai.guo@linux.dev>
On 9/23/24 10:07, George Guo wrote:
> From: George Guo <guodongtai@kylinos.cn>
>
> add a comment to doi_remove in struct netlbl_calipso_ops.
>
> Flagged by ./scripts/kernel-doc -none.
>
> Signed-off-by: George Guo <guodongtai@kylinos.cn>
## Form letter - net-next-closed
The merge window for v6.12 and therefore net-next is closed for new
drivers, features, code refactoring and optimizations. We are currently
accepting bug fixes only.
Please repost when net-next reopens after Sept 30th.
RFC patches sent for review only are obviously welcome at any time.
See:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
next prev parent reply other threads:[~2024-09-24 10:43 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 [this message]
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
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=0667f18b-2228-4201-9da7-0e3536bae321@redhat.com \
--to=pabeni@redhat.com \
--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=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).