From: <Arun.Ramadoss@microchip.com>
To: <kuba@kernel.org>, <davem@davemloft.net>
Cc: <olteanv@gmail.com>, <andrew@lunn.ch>, <claudiu.manoil@nxp.com>,
<dqfext@gmail.com>, <Woojung.Huh@microchip.com>,
<linux-renesas-soc@vger.kernel.org>,
<angelogioacchino.delregno@collabora.com>,
<clement.leger@bootlin.com>, <UNGLinuxDriver@microchip.com>,
<edumazet@google.com>, <pabeni@redhat.com>,
<arinc.unal@arinc9.com>, <alexandre.belloni@bootlin.com>,
<daniel@makrotopia.org>, <hauke@hauke-m.de>,
<sean.wang@mediatek.com>, <kurt@linutronix.de>,
<netdev@vger.kernel.org>, <george.mccollister@gmail.com>,
<matthias.bgg@gmail.com>, <Landen.Chao@mediatek.com>,
<f.fainelli@gmail.com>
Subject: Re: [PATCH net-next] net: fill in MODULE_DESCRIPTION()s for DSA tags
Date: Fri, 5 Jan 2024 02:42:24 +0000 [thread overview]
Message-ID: <ba7897934c8e42590420c278c70ac773a25afd6d.camel@microchip.com> (raw)
In-Reply-To: <20240104143759.1318137-1-kuba@kernel.org>
On Thu, 2024-01-04 at 06:37 -0800, Jakub Kicinski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> W=1 builds now warn if module is built without a
> MODULE_DESCRIPTION().
> Add descriptions to all the DSA tag modules.
>
> The descriptions are copy/pasted Kconfig names, with s/^Tag/DSA tag/.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>
next prev parent reply other threads:[~2024-01-05 2:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 14:37 [PATCH net-next] net: fill in MODULE_DESCRIPTION()s for DSA tags Jakub Kicinski
2024-01-04 14:53 ` Vladimir Oltean
2024-01-04 15:07 ` Andrew Lunn
2024-01-04 17:21 ` Florian Fainelli
2024-01-05 2:42 ` Arun.Ramadoss [this message]
2024-01-05 9:53 ` Arınç ÜNAL
2024-01-05 10:15 ` Kurt Kanzenbach
2024-01-05 16:10 ` 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=ba7897934c8e42590420c278c70ac773a25afd6d.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=Landen.Chao@mediatek.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arinc.unal@arinc9.com \
--cc=claudiu.manoil@nxp.com \
--cc=clement.leger@bootlin.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.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.