From: Paolo Abeni <pabeni@redhat.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH net-next v2 0/4] net: phy: EEE fixes
Date: Tue, 21 Feb 2023 12:52:48 +0100 [thread overview]
Message-ID: <0c1eaa274b2ef6d63f9f0897024974309a375b4b.camel@redhat.com> (raw)
In-Reply-To: <feb4388052a3f55a869704f204faa7ad39aeff1d.camel@redhat.com>
On Tue, 2023-02-21 at 12:45 +0100, Paolo Abeni wrote:
> On Tue, 2023-02-21 at 06:03 +0100, Oleksij Rempel wrote:
> > changes v2:
> > - restore previous ethtool set logic for the case where advertisements
> > are not provided by user space.
> > - use ethtool_convert_legacy_u32_to_link_mode() where possible
> > - genphy_c45_an_config_eee_aneg(): move adv initialization in to the if
> > scope.
> >
> > Different EEE related fixes.
> >
> > Oleksij Rempel (4):
> > net: phy: c45: use "supported_eee" instead of supported for access
> > validation
> > net: phy: c45: add genphy_c45_an_config_eee_aneg() function
> > net: phy: do not force EEE support
> > net: phy: c45: genphy_c45_ethtool_set_eee: validate EEE link modes
> >
> > drivers/net/phy/phy-c45.c | 55 ++++++++++++++++++++++++++++--------
> > drivers/net/phy/phy_device.c | 21 +++++++++++++-
> > include/linux/phy.h | 6 ++++
> > 3 files changed, 69 insertions(+), 13 deletions(-)
> >
> # Form letter - net-next is closed
>
> The merge window for v6.3 has begun and therefore net-next is closed
> for new drivers, features, code refactoring and optimizations.
> We are currently accepting bug fixes only.
>
> Please repost when net-next reopens after Mar 6th.
>
> RFC patches sent for review only are obviously welcome at any time.
It looks like I was a little too hasty here; these are fixes for code
currently only on net-next. As such you can re-post (for -net) after
that Linus's net-next pull and subsequent merge into -net.
Thanks,
Paolo
prev parent reply other threads:[~2023-02-21 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 5:03 Oleksij Rempel
2023-02-21 5:03 ` [PATCH net-next v2 1/4] net: phy: c45: use "supported_eee" instead of supported for access validation Oleksij Rempel
2023-02-21 5:03 ` [PATCH net-next v2 2/4] net: phy: c45: add genphy_c45_an_config_eee_aneg() function Oleksij Rempel
2023-02-21 11:57 ` Paolo Abeni
2023-02-21 5:03 ` [PATCH net-next v2 3/4] net: phy: do not force EEE support Oleksij Rempel
2023-02-21 5:03 ` [PATCH net-next v2 4/4] net: phy: c45: genphy_c45_ethtool_set_eee: validate EEE link modes Oleksij Rempel
2023-02-21 9:36 ` [PATCH net-next v2 0/4] net: phy: EEE fixes Russell King (Oracle)
2023-02-21 9:48 ` Oleksij Rempel
2023-02-21 9:52 ` Russell King (Oracle)
2023-02-21 11:45 ` Paolo Abeni
2023-02-21 11:52 ` Paolo Abeni [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=0c1eaa274b2ef6d63f9f0897024974309a375b4b.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
/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®