[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251120072118.60f64ee7@kernel.org>
Date: Thu, 20 Nov 2025 07:21:18 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Dmitry Skorodumov <skorodumov.dmitry@...wei.com>
Cc: Eric Dumazet <edumazet@...gle.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <andrey.bokhanko@...wei.com>, Andrew Lunn
<andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Paolo
Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next 05/13] ipvlan: Fix compilation warning about
__be32 -> u32
On Thu, 20 Nov 2025 14:15:07 +0300 Dmitry Skorodumov wrote:
> On 19.11.2025 04:26, Jakub Kicinski wrote:
> > On Tue, 18 Nov 2025 04:47:03 -0800 Eric Dumazet wrote:
> >> On Tue, Nov 18, 2025 at 2:01 AM Dmitry Skorodumov
> >> This is not a compilation warning, but a sparse related one ?
> >>
> >> This patch does not belong to this series, this is a bit distracting.
> >>
> >> Send a standalone patch targeting net tree, with an appropriate Fixes: tag
> >>
> >> Fixes: 2ad7bf363841 ("ipvlan: Initial check-in of the IPVLAN driver.")
> > Not sure we should be sending Linus "fixes" for false positive sparse
> > warnings at rc7/final..
>
> Not sure how to proceed! Is it op if I send this path as "net-next"?
Dunno what's "op", but try net-next again if nobody disagrees with me.
Powered by blists - more mailing lists