From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 00/10] Fix MODULE_DESCRIPTION() for net (p1)
Date: Thu, 11 Jan 2024 16:14:00 -0800 [thread overview]
Message-ID: <20240111161400.067dd107@kernel.org> (raw)
In-Reply-To: <20240108181610.2697017-1-leitao@debian.org>
On Mon, 8 Jan 2024 10:16:00 -0800 Breno Leitao wrote:
> There are hundreds of network modules that misses MODULE_DESCRIPTION(),
> causing a warnning when compiling with W=1. Example:
>
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/arcnet/com90io.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/arcnet/arc-rimi.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/arcnet/com20020.o
>
> I am working with Jakub to address them, and eventually get a clean W=1
> build.
As discussed with Paolo offline I'll cherry-pick the patches which
were good from here for net. Because these warnings are generated
at linking time they _all_ pop up on _every_ build our bots do, even
if it's an incremental build touching a tiny corner of the kernel.
--
pw-bot: ur
next prev parent reply other threads:[~2024-01-12 0:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 18:16 [PATCH net-next 00/10] Fix MODULE_DESCRIPTION() for net (p1) Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 01/10] net: fill in MODULE_DESCRIPTION()s for 8390 Breno Leitao
2024-01-09 11:25 ` Geert Uytterhoeven
2024-01-09 14:29 ` Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 02/10] net: fill in MODULE_DESCRIPTION()s for SLIP Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 03/10] net: fill in MODULE_DESCRIPTION()s for HSR Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 04/10] net: fill in MODULE_DESCRIPTION()s for NFC Breno Leitao
2024-01-08 18:57 ` Krzysztof Kozlowski
2024-01-08 18:16 ` [PATCH net-next 05/10] net: fill in MODULE_DESCRIPTION()s for Sun RPC Breno Leitao
2024-01-08 21:49 ` Jeff Layton
2024-01-08 18:16 ` [PATCH net-next 06/10] net: fill in MODULE_DESCRIPTION()s for ieee802154 Breno Leitao
2024-01-09 7:25 ` Stefan Schmidt
2024-01-09 14:29 ` Breno Leitao
2024-01-24 16:48 ` Miquel Raynal
2024-01-25 10:00 ` Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 07/10] net: fill in MODULE_DESCRIPTION()s for 6LoWPAN Breno Leitao
2024-01-10 1:04 ` Alexander Aring
2024-01-10 1:05 ` Alexander Aring
2024-01-10 9:19 ` Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 08/10] net: fill in MODULE_DESCRIPTION()s for ds26522 module Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 09/10] net: fill in MODULE_DESCRIPTION()s for s2io Breno Leitao
2024-01-08 18:16 ` [PATCH net-next 10/10] net: fill in MODULE_DESCRIPTION()s for PCS Layer Breno Leitao
2024-01-08 19:21 ` Andrew Lunn
2024-01-10 11:48 ` Breno Leitao
2024-01-09 8:01 ` [PATCH net-next 00/10] Fix MODULE_DESCRIPTION() for net (p1) Paolo Abeni
2024-01-12 0:14 ` Jakub Kicinski [this message]
2024-01-12 0:30 ` 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=20240111161400.067dd107@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=leitao@debian.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).