From: Breno Leitao <leitao@debian.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Paolo Abeni" <pabeni@redhat.com>,
dsahern@kernel.org, weiwan@google.com,
"open list:BROADCOM BCM4908 ETHERNET DRIVER"
<netdev@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 04/22] net: fill in MODULE_DESCRIPTION()s for Broadcom bgmac
Date: Mon, 22 Jan 2024 11:01:44 -0800 [thread overview]
Message-ID: <Za67mLGJ86qpt1St@gmail.com> (raw)
In-Reply-To: <4eff5139-b5ed-46a5-accb-5b2fea9ab212@broadcom.com>
On Mon, Jan 22, 2024 at 10:50:32AM -0800, Florian Fainelli wrote:
> On 1/22/24 10:45, Breno Leitao wrote:
> > W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> > Add descriptions to the Broadcom iProc GBit driver.
> >
> > Signed-off-by: Breno Leitao <leitao@debian.org>
> > ---
> > drivers/net/ethernet/broadcom/bcm4908_enet.c | 1 +
> > drivers/net/ethernet/broadcom/bgmac-bcma-mdio.c | 1 +
> > drivers/net/ethernet/broadcom/bgmac-bcma.c | 1 +
> > drivers/net/ethernet/broadcom/bgmac-platform.c | 1 +
> > drivers/net/ethernet/broadcom/bgmac.c | 1 +
> > 5 files changed, 5 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/broadcom/bcm4908_enet.c b/drivers/net/ethernet/broadcom/bcm4908_enet.c
> > index 3e7c8671cd11..a6bc5ce70230 100644
> > --- a/drivers/net/ethernet/broadcom/bcm4908_enet.c
> > +++ b/drivers/net/ethernet/broadcom/bcm4908_enet.c
> > @@ -793,5 +793,6 @@ static struct platform_driver bcm4908_enet_driver = {
> > };
> > module_platform_driver(bcm4908_enet_driver);
> > +MODULE_DESCRIPTION("Broadcom iProc GBit Ethernet driver");
>
> This should be:
>
> Broadcom BCM4908 Gigabit Ethernet driver
Thanks. I will update in v2.
next prev parent reply other threads:[~2024-01-22 19:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240122184543.2501493-1-leitao@debian.org>
2024-01-22 18:45 ` [PATCH net-next 01/22] net: fill in MODULE_DESCRIPTION()s for 8390 Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 02/22] net: fill in MODULE_DESCRIPTION()s for ieee802154 Breno Leitao
2024-01-24 16:51 ` Miquel Raynal
2024-01-25 10:01 ` Breno Leitao
2024-01-25 14:55 ` Miquel Raynal
2024-01-25 15:36 ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 03/22] net: fill in MODULE_DESCRIPTION()s for PCS Layer Breno Leitao
2024-01-22 19:31 ` Daniel Golle
2024-01-22 19:42 ` Breno Leitao
2024-01-22 19:33 ` Andrew Lunn
2024-01-22 19:42 ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 04/22] net: fill in MODULE_DESCRIPTION()s for Broadcom bgmac Breno Leitao
2024-01-22 18:50 ` Florian Fainelli
2024-01-22 19:01 ` Breno Leitao [this message]
2024-01-22 18:45 ` [PATCH net-next 05/22] net: fill in MODULE_DESCRIPTION()s for liquidio Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 06/22] net: fill in MODULE_DESCRIPTION()s for ep93xxx_eth Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 07/22] net: fill in MODULE_DESCRIPTION()s for nps_enet Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 08/22] net: fill in MODULE_DESCRIPTION()s for enetc Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 09/22] net: fill in MODULE_DESCRIPTION()s for fec Breno Leitao
2024-01-23 1:33 ` Wei Fang
2024-01-22 18:45 ` [PATCH net-next 10/22] net: fill in MODULE_DESCRIPTION()s for fsl_pq_mdio Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 11/22] net: fill in MODULE_DESCRIPTION()s for litex Breno Leitao
2024-01-22 20:48 ` Gabriel L. Somlo
2024-01-22 18:45 ` [PATCH net-next 12/22] net: fill in MODULE_DESCRIPTION()s for rvu_mbox Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 13/22] net: fill in MODULE_DESCRIPTION()s for encx24j600 Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 14/22] net: fill in MODULE_DESCRIPTION()s for ocelot Breno Leitao
2024-01-23 7:40 ` Horatiu Vultur
2024-01-23 7:48 ` Alexandre Belloni
2024-01-23 15:42 ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 15/22] net: fill in MODULE_DESCRIPTION()s for SMSC drivers Breno Leitao
2024-01-28 14:58 ` Andy Shevchenko
2024-01-22 18:45 ` [PATCH net-next 16/22] net: fill in MODULE_DESCRIPTION()s for Qualcom drivers Breno Leitao
2024-01-22 19:35 ` Subash Abhinov Kasiviswanathan (KS)
2024-01-22 18:45 ` [PATCH net-next 17/22] net: fill in MODULE_DESCRIPTION()s for Broadcom WLAN Breno Leitao
2024-01-23 6:38 ` Kalle Valo
2024-01-27 8:26 ` Arend van Spriel
2024-01-29 9:12 ` Breno Leitao
2024-01-23 11:47 ` Kalle Valo
2024-01-22 18:45 ` [PATCH net-next 18/22] net: fill in MODULE_DESCRIPTION()s for wlcore Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 19/22] net: fill in MODULE_DESCRIPTION()s for wl1251 and wl12xx Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 20/22] net: fill in MODULE_DESCRIPTION()s for dwmac-socfpga Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 21/22] net: fill in MODULE_DESCRIPTION()s for cpsw-common Breno Leitao
2024-01-23 9:50 ` Roger Quadros
2024-01-22 18:45 ` [PATCH net-next 22/22] net: fill in MODULE_DESCRIPTION()s for ec_bhf Breno Leitao
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=Za67mLGJ86qpt1St@gmail.com \
--to=leitao@debian.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
--cc=weiwan@google.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