[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250221142650.3c74dcac@kernel.org>
Date: Fri, 21 Feb 2025 14:26:50 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Damato <jdamato@...tly.com>
Cc: Kurt Kanzenbach <kurt@...utronix.de>, Tony Nguyen
<anthony.l.nguyen@...el.com>, Przemek Kitszel
<przemyslaw.kitszel@...el.com>, Andrew Lunn <andrew+netdev@...n.ch>, "David
S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Sebastian Andrzej Siewior
<bigeasy@...utronix.de>, Gerhard Engleder <gerhard@...leder-embedded.com>,
intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org
Subject: Re: [PATCH iwl-next v2 0/4] igb: XDP/ZC follow up
On Fri, 21 Feb 2025 15:53:26 -0500 Joe Damato wrote:
> > No strong preference. If rtnl_lock is not causing any issues
> > in this driver, the we can merge as is. I haven't followed
> > the past discussions, tho.
>
> Don't mean to side-track this thread, but does this mean you've
> changed your mind on the previous virtio_net thread [1] ?
>
> Or maybe I'm just misreading your response there? And instead I
> could re-spin the virtio_net but dropping the first patch and
> dealing with RTNL in the code like this series is doing?
>
> For some reason I was under the impression that the virtio_net
> series and others like it (like this igb series) were being held
> back until locking work Stanislav is doing is done.
>
> [1]: https://lore.kernel.org/netdev/20250127133756.413efb24@kernel.org/
Yes, you can probably respin v1. Let's not block this.
Powered by blists - more mailing lists