From: Jakub Kicinski <kuba@kernel.org>
To: Yangfl <mmyangfl@gmail.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@linaro.org>,
David Laight <david.laight.linux@gmail.com>
Subject: Re: [PATCH net-next v6 1/3] net: dsa: yt921x: Fix MIB overflow wraparound routine
Date: Thu, 22 Jan 2026 07:21:55 -0800 [thread overview]
Message-ID: <20260122072155.127f0c78@kernel.org> (raw)
In-Reply-To: <CAAXyoMPfQnrYWX_5LPr=vODQcg1Nx1-=rk7+6SSHZ6EqpXH69g@mail.gmail.com>
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).
next prev parent reply other threads:[~2026-01-22 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 1:30 [PATCH net-next v6 0/3] net: dsa: yt921x: Fix MIB overflow wraparound routine David Yang
2026-01-18 1:30 ` [PATCH net-next v6 1/3] " David Yang
2026-01-22 9:41 ` Paolo Abeni
2026-01-22 13:19 ` Yangfl
2026-01-22 15:21 ` Jakub Kicinski [this message]
2026-01-18 1:30 ` [PATCH net-next v6 2/3] net: dsa: yt921x: Return early for failed MIB read David Yang
2026-01-18 16:06 ` Andrew Lunn
2026-01-18 19:24 ` Yangfl
2026-01-22 9:58 ` Paolo Abeni
2026-01-18 1:30 ` [PATCH net-next v6 3/3] net: dsa: yt921x: Use u64_stats_t for MIB stats David Yang
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=20260122072155.127f0c78@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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