From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] kernel-doc: support DECLARE_PHY_INTERFACE_MASK()
Date: Wed, 13 Apr 2022 12:09:29 +0100 [thread overview]
Message-ID: <Ylavaf+OlgTVeI6a@shell.armlinux.org.uk> (raw)
In-Reply-To: <20211030020813.32654-1-rdunlap@infradead.org>
On Fri, Oct 29, 2021 at 07:08:13PM -0700, Randy Dunlap wrote:
> Support the DECLARE_PHY_INTERFACE_MASK() macro that is used to declare
> a bitmap by converting the macro to DECLARE_BITMAP(), as has been done
> for the __ETHTOOL_DECLARE_LINK_MODE_MASK() macro.
>
> This fixes a 'make htmldocs' warning:
>
> include/linux/phylink.h:82: warning: Function parameter or member 'DECLARE_PHY_INTERFACE_MASK(supported_interfaces' not described in 'phylink_config'
>
> that was introduced by commit
> 38c310eb46f5 ("net: phylink: add MAC phy_interface_t bitmap")
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Russell King (Oracle) <linux@armlinux.org.uk>
Thanks Randy, sorry I missed this patch.
Reviewed-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
What is the intention for merging this patch? Will Jon merge it?
Your tags said To: Jon but you don't seem to have included him in
the email.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-04-13 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 2:08 [PATCH] kernel-doc: support DECLARE_PHY_INTERFACE_MASK() Randy Dunlap
2022-04-13 11:09 ` Russell King (Oracle) [this message]
2022-04-13 15:19 ` Randy Dunlap
2022-04-14 1:29 ` Randy Dunlap
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=Ylavaf+OlgTVeI6a@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.