From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Woojung Huh <woojung.huh@microchip.com>,
Simon Horman <horms@kernel.org>,
Thangaraj Samynathan <Thangaraj.S@microchip.com>,
netdev@vger.kernel.org, Phil Elwell <phil@raspberrypi.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-kernel@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
kernel@pengutronix.de,
Rengarajan Sundararajan <Rengarajan.S@microchip.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v1 1/1] net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect
Date: Thu, 26 Jun 2025 11:29:54 -0700 [thread overview]
Message-ID: <20250626112954.5987f2e9@kernel.org> (raw)
In-Reply-To: <aF0edQRJAXSps5CV@pengutronix.de>
On Thu, 26 Jun 2025 12:18:29 +0200 Oleksij Rempel wrote:
> > > This patch is intended for `net-next` since the issue existed before the
> > > PHYLINK migration, but is more naturally and cleanly addressed now that
> > > PHYLINK manages link state transitions.
> >
> > And repost that for net, please.. :)
>
> It will be not compatible with the PHYlink migration patch in the
> net-next. Should i wait until PHYlink patch goes to the net and then
> send different patch variants for stable before PHYlink migration and
> after?
The conflict will be relatively easy, we will have to cope.
But you really, really should hold off net-next patches until
you fix all the pre-existing bugs :|
prev parent reply other threads:[~2025-06-26 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 8:51 [PATCH net-next v1 1/1] net: usb: lan78xx: fix WARN in __netif_napi_del_locked on disconnect Oleksij Rempel
2025-06-23 23:55 ` Jakub Kicinski
2025-06-26 10:18 ` Oleksij Rempel
2025-06-26 18:29 ` Jakub Kicinski [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=20250626112954.5987f2e9@kernel.org \
--to=kuba@kernel.org \
--cc=Rengarajan.S@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=phil@raspberrypi.org \
--cc=rmk+kernel@armlinux.org.uk \
--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 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.