From: Andrew Lunn <andrew@lunn.ch>
To: Breno Leitao <leitao@debian.org>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
horms@kernel.org
Subject: Re: [PATCH net v2 6/7] net: fill in MODULE_DESCRIPTION()s for mdio_devres
Date: Wed, 14 Feb 2024 16:52:13 +0100 [thread overview]
Message-ID: <ace91887-8c82-4df9-a62c-99d30e1b28e4@lunn.ch> (raw)
In-Reply-To: <20240214152741.670178-7-leitao@debian.org>
On Wed, Feb 14, 2024 at 07:27:40AM -0800, Breno Leitao wrote:
> W=1 builds now warn if module is built without a MODULE_DESCRIPTION().
> Add descriptions to the PHY MDIO helpers.
>
> Suggested-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2024-02-14 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 15:27 [PATCH net v2 0/7] Fix MODULE_DESCRIPTION() for net (p6) Breno Leitao
2024-02-14 15:27 ` [PATCH net v2 1/7] net: fill in MODULE_DESCRIPTION()s for xen-netback Breno Leitao
2024-02-14 15:27 ` [PATCH net v2 2/7] net: fill in MODULE_DESCRIPTION()s for ieee802154/fakelb Breno Leitao
2024-02-19 10:47 ` Miquel Raynal
2024-02-14 15:27 ` [PATCH net v2 3/7] net: fill in MODULE_DESCRIPTION()s for plip Breno Leitao
2024-02-14 15:27 ` [PATCH net v2 4/7] net: fill in MODULE_DESCRIPTION()s for fddik/skfp Breno Leitao
2024-02-14 15:27 ` [PATCH net v2 5/7] net: fill in MODULE_DESCRIPTION()s for ppp Breno Leitao
2024-02-14 15:27 ` [PATCH net v2 6/7] net: fill in MODULE_DESCRIPTION()s for mdio_devres Breno Leitao
2024-02-14 15:52 ` Andrew Lunn [this message]
2024-02-14 15:27 ` [PATCH net v2 7/7] net: fill in MODULE_DESCRIPTION()s for missing arcnet Breno Leitao
2024-02-15 16:10 ` [PATCH net v2 0/7] Fix MODULE_DESCRIPTION() for net (p6) 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=ace91887-8c82-4df9-a62c-99d30e1b28e4@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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.