From: Simon Horman <simon.horman@corigine.com>
To: Robert Hancock <robert.hancock@calian.com>
Cc: Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Move KSZ9477 errata handling to PHY driver
Date: Sat, 3 Jun 2023 16:30:30 +0200 [thread overview]
Message-ID: <ZHtOhhH/+XrcbxFs@corigine.com> (raw)
In-Reply-To: <20230602234019.436513-1-robert.hancock@calian.com>
On Fri, Jun 02, 2023 at 05:40:17PM -0600, Robert Hancock wrote:
> Patches to move handling for KSZ9477 PHY errata register fixes from
> the DSA switch driver into the corresponding PHY driver, for more
> proper layering and ordering.
>
> Robert Hancock (2):
> net: phy: micrel: Move KSZ9477 errata fixes to PHY driver
> net: dsa: microchip: remove KSZ9477 PHY errata handling
Hi Robert,
this series does not seem to apply to net-next.
Please rebase on to of net-next and repost as v2.
And please include the Reviewed-by tags from Andrew Lunn in v2,
assuming there are no other changes.
--
pw-bot: rc
prev parent reply other threads:[~2023-06-03 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 23:40 Robert Hancock
2023-06-02 23:40 ` [PATCH net-next 1/2] net: phy: micrel: Move KSZ9477 errata fixes " Robert Hancock
2023-06-03 14:16 ` Andrew Lunn
2023-06-02 23:40 ` [PATCH net-next 2/2] net: dsa: microchip: remove KSZ9477 PHY errata handling Robert Hancock
2023-06-03 14:16 ` Andrew Lunn
2023-06-03 0:04 ` [PATCH net-next 0/2] Move KSZ9477 errata handling to PHY driver Andrew Lunn
2023-06-03 0:13 ` Robert Hancock
2023-06-03 14:30 ` Simon Horman [this message]
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=ZHtOhhH/+XrcbxFs@corigine.com \
--to=simon.horman@corigine.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robert.hancock@calian.com \
--cc=woojung.huh@microchip.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
all inboxes | Powered by JetHome®