[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260122072155.127f0c78@kernel.org>
Date: Thu, 22 Jan 2026 07:21:55 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Yangfl <mmyangfl@...il.com>
Cc: Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org, Andrew Lunn
<andrew@...n.ch>, Vladimir Oltean <olteanv@...il.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
linux-kernel@...r.kernel.org, Dan Carpenter <dan.carpenter@...aro.org>,
David Laight <david.laight.linux@...il.com>
Subject: Re: [PATCH net-next v6 1/3] net: dsa: yt921x: Fix MIB overflow
wraparound routine
On Thu, 22 Jan 2026 21:19:29 +0800 Yangfl wrote:
> > Why targeting net-next here? the blamed commit is already in Linus'tree
> > and it looks like the above could causes functional issues, ad the wrong
> > value is written into the mib.
> >
> > I think this should go via net.
>
> There are following patches which are not fully suitable for net tree,
> and the issue does not block the main functionality, only gives wrong
> statistics.
>
> Should the whole series be sent to net, or split into two parts?
Split into two parts please (and the second one posted after net is
merged back into net-next).
Powered by blists - more mailing lists