From: Michael Walle <michael@walle.cc>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "Russell King (Oracle)" <linux@armlinux.org.uk>,
netdev@vger.kernel.org, Antoine Tenart <atenart@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Maxim Kochetkov <fido_max@inbox.ru>,
Bjarni Jonasson <bjarni.jonasson@microchip.com>,
Steen Hegelund <steen.hegelund@microchip.com>,
UNGLinuxDriver@microchip.com,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [RFC PATCH v2 net-next 0/5] Let phylink manage in-band AN for the PHY
Date: Thu, 16 Sep 2021 16:05:20 +0200 [thread overview]
Message-ID: <c5e4b74c3f7988bedbd74270021b4fb4@walle.cc> (raw)
In-Reply-To: <20210916135445.euovk2aelndgtvid@skbuf>
Am 2021-09-16 15:54, schrieb Vladimir Oltean:
> On Thu, Sep 16, 2021 at 03:51:28PM +0200, Michael Walle wrote:
>> Am 2021-09-16 15:09, schrieb Vladimir Oltean:
>> > On Mon, Aug 30, 2021 at 09:36:23PM +0300, Vladimir Oltean wrote:
>> > > On Mon, Aug 30, 2021 at 07:30:15PM +0100, Russell King (Oracle) wrote:
>> > > > Can we postpone this after this merge window please, so I've got time
>> > > > to properly review this. Thanks.
>> > >
>> > > Please review at your discretion, I've no intention to post a v3 right
>> > > now, and to the best of my knowledge, RFC's are not even considered
>> > > for
>> > > direct inclusion in the git tree.
>> >
>> > Hello Russell, can you please review these patches if possible? I
>> > would like to repost them soon.
>>
>> I planned to test this on my board with the AR8031 (and add support
>> there),
>> but it seems I won't find time before my vacation, unfortunately.
>
> Oh, but there isn't any "support" to be added I though, your conclusion
> last time seemed to be that it only supported in-band autoneg ON?
> I was going to add a patch to implement .validate_inband_aneg for the
> at803x driver to mark that fact too, I just didn't do it in the RFC.
> That should also fix the ENETC ports on the LS1028A-RDB which were
> migrated to phylink while they didn't have the 'managed =
> "in-band-status"'
> OF property, and enable new kernels to still work with the old DT blob.
> Or were you thinking of something else?
No, but I won't find time to test it within the next.. uhm, 30minutes
until I call it a day ;)
-michael
next prev parent reply other threads:[~2021-09-16 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 15:52 [RFC PATCH v2 net-next 0/5] Let phylink manage in-band AN for the PHY Vladimir Oltean
2021-08-30 15:52 ` [RFC PATCH v2 net-next 1/5] net: phylink: pass the phy argument to phylink_sfp_config Vladimir Oltean
2021-08-30 15:52 ` [RFC PATCH v2 net-next 2/5] net: phylink: introduce a generic method for querying PHY in-band autoneg capability Vladimir Oltean
2021-08-30 15:52 ` [RFC PATCH v2 net-next 3/5] net: phy: bcm84881: move the in-band capability check where it belongs Vladimir Oltean
2021-08-30 15:52 ` [RFC PATCH v2 net-next 4/5] net: phylink: explicitly configure in-band autoneg for PHYs that support it Vladimir Oltean
2021-08-30 15:52 ` [RFC PATCH v2 net-next 5/5] net: phy: mscc: configure in-band auto-negotiation for VSC8514 Vladimir Oltean
2021-08-30 18:30 ` [RFC PATCH v2 net-next 0/5] Let phylink manage in-band AN for the PHY Russell King (Oracle)
2021-08-30 18:36 ` Vladimir Oltean
2021-09-16 13:09 ` Vladimir Oltean
2021-09-16 13:51 ` Michael Walle
2021-09-16 13:54 ` Vladimir Oltean
2021-09-16 14:05 ` Michael Walle [this message]
2021-09-16 14:07 ` Vladimir Oltean
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=c5e4b74c3f7988bedbd74270021b4fb4@walle.cc \
--to=michael@walle.cc \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bjarni.jonasson@microchip.com \
--cc=f.fainelli@gmail.com \
--cc=fido_max@inbox.ru \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=steen.hegelund@microchip.com \
--cc=vladimir.oltean@nxp.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.