From: Roger Quadros <rogerq@kernel.org>
To: Breno Leitao <leitao@debian.org>,
kuba@kernel.org, davem@davemloft.net, abeni@redhat.com,
edumazet@google.com, Siddharth Vadapalli <s-vadapalli@ti.com>,
Ravi Gunasekaran <r-gunasekaran@ti.com>,
Paolo Abeni <pabeni@redhat.com>
Cc: dsahern@kernel.org, weiwan@google.com,
Rob Herring <robh@kernel.org>, Alex Elder <elder@linaro.org>,
Simon Horman <horms@kernel.org>,
"open list:TI ETHERNET SWITCH DRIVER (CPSW)"
<linux-omap@vger.kernel.org>,
"open list:TI ETHERNET SWITCH DRIVER (CPSW)"
<netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 21/22] net: fill in MODULE_DESCRIPTION()s for cpsw-common
Date: Tue, 23 Jan 2024 11:50:13 +0200 [thread overview]
Message-ID: <50f79727-d82a-4122-9b3e-66dd09027ab5@kernel.org> (raw)
In-Reply-To: <20240122184543.2501493-22-leitao@debian.org>
On 22/01/2024 20:45, Breno Leitao wrote:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> Add descriptions to the TI CPSW switch module.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> drivers/net/ethernet/ti/cpsw-common.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ethernet/ti/cpsw-common.c b/drivers/net/ethernet/ti/cpsw-common.c
> index 26dc906eae90..57fe936bb177 100644
> --- a/drivers/net/ethernet/ti/cpsw-common.c
> +++ b/drivers/net/ethernet/ti/cpsw-common.c
> @@ -90,4 +90,5 @@ int ti_cm_get_macid(struct device *dev, int slave, u8 *mac_addr)
> }
> EXPORT_SYMBOL_GPL(ti_cm_get_macid);
>
> +MODULE_DESCRIPTION("TI CPSW Switch common module");
> MODULE_LICENSE("GPL");
Reviewed-by: Roger Quadros <rogerq@kernel.org>
--
cheers,
-roger
prev parent reply other threads:[~2024-01-23 9:50 UTC|newest]
Thread overview: 2+ 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 21/22] net: fill in MODULE_DESCRIPTION()s for cpsw-common Breno Leitao
2024-01-23 9:50 ` Roger Quadros [this message]
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=50f79727-d82a-4122-9b3e-66dd09027ab5@kernel.org \
--to=rogerq@kernel.org \
--cc=abeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=elder@linaro.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).