[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191122092136.GJ25745@shell.armlinux.org.uk>
Date: Fri, 22 Nov 2019 09:21:37 +0000
From: Russell King - ARM Linux admin <linux@...linux.org.uk>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: David Miller <davem@...emloft.net>, andrew@...n.ch,
nbd@...nwrt.org, radhey.shyam.pandey@...inx.com,
alexandre.torgue@...com, netdev@...r.kernel.org,
sean.wang@...iatek.com, linux-stm32@...md-mailman.stormreply.com,
vivien.didelot@...il.com, michal.simek@...inx.com,
joabreu@...opsys.com, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, thomas.petazzoni@...tlin.com,
john@...ozen.org, matthias.bgg@...il.com, peppe.cavallaro@...com,
Mark-MC.Lee@...iatek.com, mcoquelin.stm32@...il.com,
hkallweit1@...il.com
Subject: Re: [CFT PATCH net-next v2] net: phylink: rename mac_link_state() op
to mac_pcs_get_state()
On Thu, Nov 21, 2019 at 07:36:44PM -0800, Florian Fainelli wrote:
>
>
> On 11/21/2019 7:14 PM, David Miller wrote:
> > From: Russell King <rmk+kernel@...linux.org.uk>
> > Date: Thu, 21 Nov 2019 00:36:22 +0000
> >
> >> Rename the mac_link_state() method to mac_pcs_get_state() to make it
> >> clear that it should be returning the MACs PCS current state, which
> >> is used for inband negotiation rather than just reading back what the
> >> MAC has been configured for. Update the documentation to explicitly
> >> mention that this is for inband.
> >>
> >> We drop the return value as well; most of phylink doesn't check the
> >> return value and it is not clear what it should do on error - instead
> >> arrange for state->link to be false.
> >>
> >> Signed-off-by: Russell King <rmk+kernel@...linux.org.uk>
> >> ---
> >> This is something I'd like to do to make it clearer what phylink
> >> expects of this function, and that it shouldn't just read-back how
> >> the MAC was configured.
> >>
> >> This version drops the deeper changes, concentrating just on the
> >> phylink API rather than delving deeper into drivers, as I haven't
> >> received any feedback on that patch.
> >>
> >> It would be nice to see all these drivers tested with this change.
> >
> > I'm tempted to just apply this, any objections?
> >
>
> Russell, which of this patch or: http://patchwork.ozlabs.org/patch/1197425/
>
> would you consider worthy of merging?
Let's go with v2 for now - it gets the rename done with less risk that
there'll be a problem. I can always do the remainder in a separate
patch after the merge window as a separate patch.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
Powered by blists - more mailing lists