From: Greg KH <gregkh@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, ulf.hansson@linaro.org, rostedt@goodmis.org,
sj@kernel.org, schspa@gmail.com, vladbu@nvidia.com,
idosch@nvidia.com
Subject: Re: [PATCH net-next 3/4] net: fill in MODULE_DESCRIPTION()s under net/802*
Date: Thu, 26 Oct 2023 21:11:43 +0200 [thread overview]
Message-ID: <2023102633-quake-nape-bffb@gregkh> (raw)
In-Reply-To: <20231026190101.1413939-4-kuba@kernel.org>
On Thu, Oct 26, 2023 at 12:01:00PM -0700, Jakub Kicinski wrote:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: ulf.hansson@linaro.org
> CC: rostedt@goodmis.org
> CC: sj@kernel.org
> CC: schspa@gmail.com
> CC: gregkh@linuxfoundation.org
> CC: vladbu@nvidia.com
> CC: idosch@nvidia.com
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2023-10-26 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 19:00 [PATCH net-next 0/4] net: fill in 18 MODULE_DESCRIPTION()s Jakub Kicinski
2023-10-26 19:00 ` [PATCH net-next 1/4] net: fill in MODULE_DESCRIPTION()s in kuba@'s modules Jakub Kicinski
2023-10-27 6:54 ` Kalle Valo
2023-10-27 14:15 ` Jonathan Bither
2023-10-27 14:28 ` Jakub Kicinski
2023-10-26 19:00 ` [PATCH net-next 2/4] net: fill in MODULE_DESCRIPTION()s under net/core Jakub Kicinski
2023-10-27 4:52 ` Oleksij Rempel
2023-10-26 19:01 ` [PATCH net-next 3/4] net: fill in MODULE_DESCRIPTION()s under net/802* Jakub Kicinski
2023-10-26 19:11 ` Greg KH [this message]
2023-10-26 19:01 ` [PATCH net-next 4/4] net: fill in MODULE_DESCRIPTION()s under drivers/net/ Jakub Kicinski
2023-10-26 20:00 ` Willem de Bruijn
2023-10-26 22:46 ` Jamal Hadi Salim
2023-10-27 6:35 ` Arnd Bergmann
2023-10-27 6:50 ` Jason Wang
2023-10-27 7:37 ` Taehee Yoo
2023-10-27 10:05 ` [PATCH net-next] net: bridge: fill in MODULE_DESCRIPTION() Nikolay Aleksandrov
2023-10-27 10:20 ` patchwork-bot+netdevbpf
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=2023102633-quake-nape-bffb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=schspa@gmail.com \
--cc=sj@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vladbu@nvidia.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).