From: Breno Leitao <leitao@debian.org>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 00/10] Fix MODULE_DESCRIPTION() for net (p1)
Date: Mon, 8 Jan 2024 10:16:00 -0800 [thread overview]
Message-ID: <20240108181610.2697017-1-leitao@debian.org> (raw)
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.
Breno Leitao (10):
net: fill in MODULE_DESCRIPTION()s for 8390
net: fill in MODULE_DESCRIPTION()s for SLIP
net: fill in MODULE_DESCRIPTION()s for HSR
net: fill in MODULE_DESCRIPTION()s for NFC
net: fill in MODULE_DESCRIPTION()s for Sun RPC
net: fill in MODULE_DESCRIPTION()s for ieee802154
net: fill in MODULE_DESCRIPTION()s for 6LoWPAN
net: fill in MODULE_DESCRIPTION()s for ds26522 module
net: fill in MODULE_DESCRIPTION()s for s2io
net: fill in MODULE_DESCRIPTION()s for PCS Layer
drivers/net/ethernet/8390/8390.c | 1 +
drivers/net/ethernet/8390/8390p.c | 1 +
drivers/net/ethernet/8390/apne.c | 1 +
drivers/net/ethernet/8390/hydra.c | 1 +
drivers/net/ethernet/8390/stnic.c | 1 +
drivers/net/ethernet/8390/zorro8390.c | 1 +
drivers/net/ethernet/neterion/s2io.c | 1 +
drivers/net/pcs/pcs-mtk-lynxi.c | 1 +
drivers/net/slip/slhc.c | 1 +
drivers/net/slip/slip.c | 1 +
drivers/net/wan/slic_ds26522.c | 1 +
net/6lowpan/core.c | 2 +-
net/hsr/hsr_main.c | 1 +
net/ieee802154/6lowpan/core.c | 1 +
net/ieee802154/socket.c | 1 +
net/nfc/digital_core.c | 1 +
net/nfc/nci/core.c | 1 +
net/nfc/nci/spi.c | 1 +
net/sunrpc/auth_gss/auth_gss.c | 1 +
net/sunrpc/auth_gss/gss_krb5_mech.c | 1 +
net/sunrpc/sunrpc_syms.c | 1 +
21 files changed, 21 insertions(+), 1 deletion(-)
--
2.39.3
next reply other threads:[~2024-01-08 18:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 18:16 Breno Leitao [this message]
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 18:16 ` Breno Leitao
2024-01-08 19:21 ` Andrew Lunn
2024-01-08 19:21 ` Andrew Lunn
2024-01-10 11:48 ` Breno Leitao
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
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=20240108181610.2697017-1-leitao@debian.org \
--to=leitao@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.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 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.