From: Andrew Lunn <andrew@lunn.ch>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
Philippe Schenker <philippe.schenker@toradex.com>
Subject: Re: [PATCH net-next v1 5/5] net: phy: micrel: ksz886x/ksz8081: add cabletest support
Date: Tue, 14 Jul 2020 15:12:40 +0200 [thread overview]
Message-ID: <20200714131240.GE1140268@lunn.ch> (raw)
In-Reply-To: <20200714072501.GA5072@pengutronix.de>
> OK. So, i'll cover both errata with separate flags? Set flags in the DSA
> driver and apply workarounds in the PHY. ACK?
Yes. Assume the issues are limited to just the first PHY in this
switch. If there are discrete PHYs with the same issue, we can come up
with a different way to identify them.
Andrew
next prev parent reply other threads:[~2020-07-14 13:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 12:08 [PATCH net-next v1 0/5] add cable test support for ksz8081 and ksz8873 Oleksij Rempel
2020-07-10 12:08 ` [PATCH net-next v1 1/5] net: phy: micrel: use consistent indention after define Oleksij Rempel
2020-07-10 13:44 ` Andrew Lunn
2020-07-10 12:08 ` [PATCH net-next v1 2/5] net: phy: micrel: apply resume errata workaround for ksz8873 and ksz8863 Oleksij Rempel
2020-07-10 13:47 ` Andrew Lunn
2020-07-10 12:08 ` [PATCH net-next v1 3/5] net: phy: micrel: ksz886x add MDI-X support Oleksij Rempel
2020-07-10 13:50 ` Andrew Lunn
2020-07-10 12:08 ` [PATCH net-next v1 4/5] net: phy: micrel: ksz8081 " Oleksij Rempel
2020-07-10 13:50 ` Andrew Lunn
2020-07-10 12:08 ` [PATCH net-next v1 5/5] net: phy: micrel: ksz886x/ksz8081: add cabletest support Oleksij Rempel
2020-07-11 18:29 ` Andrew Lunn
2020-07-13 4:11 ` Oleksij Rempel
2020-07-13 8:50 ` Oleksij Rempel
2020-07-13 15:17 ` Andrew Lunn
2020-07-14 7:25 ` Oleksij Rempel
2020-07-14 13:12 ` Andrew Lunn [this message]
2020-07-24 9:15 ` Oleksij Rempel
2020-07-11 18:33 ` Andrew Lunn
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=20200714131240.GE1140268@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=philippe.schenker@toradex.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 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).