From: Taehee Yoo <ap420073@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
jhs@mojatatu.com, arnd@arndb.de, willemdebruijn.kernel@gmail.com,
jasowang@redhat.com
Subject: Re: [PATCH net-next 4/4] net: fill in MODULE_DESCRIPTION()s under drivers/net/
Date: Fri, 27 Oct 2023 16:37:31 +0900 [thread overview]
Message-ID: <c18bb733-9ce5-ad32-acfa-370f72cf5efc@gmail.com> (raw)
In-Reply-To: <20231026190101.1413939-5-kuba@kernel.org>
On 10/27/23 04:01, Jakub Kicinski wrote:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
Acked-by: Taehee Yoo <ap420073@gmail.com>
next prev parent reply other threads:[~2023-10-27 7:37 UTC|newest]
Thread overview: 19+ 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
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 [this message]
2023-10-27 10:05 ` [Bridge] [PATCH net-next] net: bridge: fill in MODULE_DESCRIPTION() Nikolay Aleksandrov
2023-10-27 10:05 ` Nikolay Aleksandrov
2023-10-27 10:20 ` [Bridge] " patchwork-bot+netdevbpf
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=c18bb733-9ce5-ad32-acfa-370f72cf5efc@gmail.com \
--to=ap420073@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.