From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Colton Lewis <colton.w.lewis@protonmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v3] net: phylink: correct trivial kernel-doc inconsistencies
Date: Sun, 28 Jun 2020 10:36:35 +0100 [thread overview]
Message-ID: <20200628093634.GQ1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200627235803.101718-1-colton.w.lewis@protonmail.com>
On Sat, Jun 27, 2020 at 11:58:09PM +0000, Colton Lewis wrote:
> Silence documentation build warnings by correcting kernel-doc
> comments. In the case of pcs_{config,an_restart,link_up}, change the
> declaration to a normal function since these only there for
> documentation anyway.
>
> ./include/linux/phylink.h:74: warning: Function parameter or member 'poll_fixed_state' not described in 'phylink_config'
> ./include/linux/phylink.h:74: warning: Function parameter or member 'get_fixed_state' not described in 'phylink_config'
> ./include/linux/phylink.h:336: warning: Function parameter or member 'pcs_config' not described in 'int'
> ./include/linux/phylink.h:336: warning: Excess function parameter 'config' description in 'int'
> ./include/linux/phylink.h:336: warning: Excess function parameter 'mode' description in 'int'
> ./include/linux/phylink.h:336: warning: Excess function parameter 'interface' description in 'int'
> ./include/linux/phylink.h:336: warning: Excess function parameter 'advertising' description in 'int'
> ./include/linux/phylink.h:345: warning: Function parameter or member 'pcs_an_restart' not described in 'void'
> ./include/linux/phylink.h:345: warning: Excess function parameter 'config' description in 'void'
> ./include/linux/phylink.h:361: warning: Function parameter or member 'pcs_link_up' not described in 'void'
> ./include/linux/phylink.h:361: warning: Excess function parameter 'config' description in 'void'
> ./include/linux/phylink.h:361: warning: Excess function parameter 'mode' description in 'void'
> ./include/linux/phylink.h:361: warning: Excess function parameter 'interface' description in 'void'
> ./include/linux/phylink.h:361: warning: Excess function parameter 'speed' description in 'void'
> ./include/linux/phylink.h:361: warning: Excess function parameter 'duplex' description in 'void'
>
> Signed-off-by: Colton Lewis <colton.w.lewis@protonmail.com>
> ---
> include/linux/phylink.h | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/phylink.h b/include/linux/phylink.h
> index cc5b452a184e..24c52d9f63d6 100644
> --- a/include/linux/phylink.h
> +++ b/include/linux/phylink.h
> @@ -62,6 +62,8 @@ enum phylink_op_type {
> * @dev: a pointer to a struct device associated with the MAC
> * @type: operation type of PHYLINK instance
> * @pcs_poll: MAC PCS cannot provide link change interrupt
> + * @poll_fixed_state: poll link state with @get_fixed_state
> + * @get_fixed_state: read link state into struct phylink_link_state
> */
> struct phylink_config {
> struct device *dev;
> @@ -331,7 +333,7 @@ void pcs_get_state(struct phylink_config *config,
> *
> * For most 10GBASE-R, there is no advertisement.
> */
> -int (*pcs_config)(struct phylink_config *config, unsigned int mode,
> +int pcs_config(struct phylink_config *config, unsigned int mode,
> phy_interface_t interface, const unsigned long *advertising);
We seem to be having a communication breakdown. In review to your
version 2 patch set, I said:
However, please drop all your changes for everything but the
"struct phylink_config" documentation change; I'm intending to change
all these method signatures, which means your changes will conflict.
But the changes still exist in version 3. What gives?
--
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:[~2020-06-28 9:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200621154248.GB338481@lunn.ch>
2020-06-21 15:53 ` FWD: [PATCH 3/3] net: phylink: correct trivial kernel-doc inconsistencies Russell King - ARM Linux admin
2020-06-21 23:02 ` Colton Lewis
2020-06-21 23:44 ` Russell King - ARM Linux admin
[not found] ` <3034206.AJdgDx1Vlc@laptop.coltonlewis.name>
2020-06-27 23:58 ` [PATCH v3] " Colton Lewis
2020-06-28 9:36 ` Russell King - ARM Linux admin [this message]
2020-06-28 21:36 ` Colton Lewis
2020-06-28 22:20 ` Russell King - ARM Linux admin
2020-06-29 4:00 ` David Miller
2020-06-28 21:39 ` [PATCH v4 1/2] net: core: " Colton Lewis
2020-06-29 3:59 ` David Miller
2020-06-28 21:39 ` [PATCH v4 2/2] " Colton Lewis
2020-06-29 3:59 ` David Miller
2020-06-22 20:07 ` [PATCH 3/3] net: phylink: " David Miller
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=20200628093634.GQ1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=colton.w.lewis@protonmail.com \
--cc=netdev@vger.kernel.org \
/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 NNTP newsgroup(s).