From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, dsahern@kernel.org, matttbe@kernel.org,
martineau@kernel.org, marcelo.leitner@gmail.com,
lucien.xin@gmail.com, kgraul@linux.ibm.com, wenjia@linux.ibm.com,
jaka@linux.ibm.com, alibuda@linux.alibaba.com,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
jmaloy@redhat.com, ying.xue@windriver.com, sgarzare@redhat.com,
bjorn@kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, kuniyu@amazon.com,
mptcp@lists.linux.dev, linux-sctp@vger.kernel.org,
linux-s390@vger.kernel.org,
tipc-discussion@lists.sourceforge.net,
virtualization@lists.linux.dev, bpf@vger.kernel.org
Subject: Re: [PATCH net] net: fill in MODULE_DESCRIPTION()s for SOCK_DIAG modules
Date: Sun, 19 Nov 2023 20:10:23 +0000 [thread overview]
Message-ID: <170042462396.21508.74186037666655435.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231119033006.442271-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 18 Nov 2023 19:30:06 -0800 you wrote:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> Add descriptions to all the sock diag modules in one fell swoop.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: dsahern@kernel.org
> CC: matttbe@kernel.org
> CC: martineau@kernel.org
> CC: marcelo.leitner@gmail.com
> CC: lucien.xin@gmail.com
> CC: kgraul@linux.ibm.com
> CC: wenjia@linux.ibm.com
> CC: jaka@linux.ibm.com
> CC: alibuda@linux.alibaba.com
> CC: tonylu@linux.alibaba.com
> CC: guwen@linux.alibaba.com
> CC: jmaloy@redhat.com
> CC: ying.xue@windriver.com
> CC: sgarzare@redhat.com
> CC: bjorn@kernel.org
> CC: magnus.karlsson@intel.com
> CC: maciej.fijalkowski@intel.com
> CC: kuniyu@amazon.com
> CC: mptcp@lists.linux.dev
> CC: linux-sctp@vger.kernel.org
> CC: linux-s390@vger.kernel.org
> CC: tipc-discussion@lists.sourceforge.net
> CC: virtualization@lists.linux.dev
> CC: bpf@vger.kernel.org
>
> [...]
Here is the summary with links:
- [net] net: fill in MODULE_DESCRIPTION()s for SOCK_DIAG modules
https://git.kernel.org/netdev/net/c/938dbead34cd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-19 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 3:30 [PATCH net] net: fill in MODULE_DESCRIPTION()s for SOCK_DIAG modules Jakub Kicinski
2023-11-19 20:10 ` patchwork-bot+netdevbpf [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=170042462396.21508.74186037666655435.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=jmaloy@redhat.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=marcelo.leitner@gmail.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tonylu@linux.alibaba.com \
--cc=virtualization@lists.linux.dev \
--cc=wenjia@linux.ibm.com \
--cc=ying.xue@windriver.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 read-only IMAP folder(s) and NNTP newsgroup(s).