From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH net-next v2 1/1] net: phy: ax88772a: fix lost pause advertisement configuration
Date: Tue, 28 Jun 2022 08:43:55 +0200 [thread overview]
Message-ID: <20220628064355.GD13092@pengutronix.de> (raw)
In-Reply-To: <20220627221705.0a49f3c9@kernel.org>
On Mon, Jun 27, 2022 at 10:17:05PM -0700, Jakub Kicinski wrote:
> On Sun, 26 Jun 2022 17:27:03 +0200 Oleksij Rempel wrote:
> > Subject: [PATCH net-next v2 1/1] net: phy: ax88772a: fix lost pause advertisement configuration
> >
> > In case of asix_ax88772a_link_change_notify() workaround, we run soft
> > reset which will automatically clear MII_ADVERTISE configuration. The
> > PHYlib framework do not know about changed configuration state of the
> > PHY, so we need use phy_init_hw() to reinit PHY configuration.
> >
> > Fixes: dde258469257 ("net: usb/phy: asix: add support for ax88772A/C PHYs")
>
> Why net-next?
It is old bug but it will be notable only after this patch:
https://lore.kernel.org/all/20220624080208.3143093-1-o.rempel@pengutronix.de/
Should I resend it to net?
Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2022-06-28 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 15:27 [PATCH net-next v2 1/1] net: phy: ax88772a: fix lost pause advertisement configuration Oleksij Rempel
2022-06-26 16:54 ` Andrew Lunn
2022-06-28 5:17 ` Jakub Kicinski
2022-06-28 6:43 ` Oleksij Rempel [this message]
2022-06-28 11:22 ` Paolo Abeni
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=20220628064355.GD13092@pengutronix.de \
--to=o.rempel@pengutronix.de \
--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=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).