From: Stanislaw Pal <kuncy7@gmail.com>
To: Yongzhao Chen <yongzhao.derek@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Christian Marangi <ansuelsmth@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Ziyang Huang <hzyitc@outlook.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v7] net: dsa: qca8k: preserve port state across MTU changes
Date: Wed, 28 Oct 2026 15:56:22 +0100 [thread overview]
Message-ID: <20261028145622.195730-1-kuncy7@gmail.com> (raw)
In-Reply-To: <20261027212505.1848-1-yongzhao.derek@gmail.com>
Hi Yongzhao,
On Tue, Oct 27, 2026 at 10:25:05PM +0100, Yongzhao Chen wrote:
> I will send v8 for net-next once it reopens and [2] is in net-next, and
> say in the commit message how the problem was found, as sinfo asked.
By the same rule my net series [1] belongs in net-next too: all three
were found by the AI review of my MIB statistics series, none in
production. So I will send its v2 to net-next once it reopens, with the
regmap locking patch first and unchanged, and you can base v8 on it. If
yours is ready first, carry that patch in your series instead and I
will drop it from mine.
[1] https://lore.kernel.org/netdev/20261022192933.384898-1-kuncy7@gmail.com/
Stanislaw
next prev parent reply other threads:[~2026-10-28 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 15:58 [PATCH net v7] net: dsa: qca8k: preserve port state across MTU changes Yongzhao Chen
2026-10-22 16:03 ` netdev-bot+sinfo
2026-10-27 9:27 ` Yongzhao Chen
2026-10-27 12:54 ` Andrew Lunn
2026-10-27 21:25 ` Yongzhao Chen
2026-10-28 14:56 ` Stanislaw Pal [this message]
2026-10-26 16:21 ` netdev-bot+sashiko
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=20261028145622.195730-1-kuncy7@gmail.com \
--to=kuncy7@gmail.com \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=horms@kernel.org \
--cc=hzyitc@outlook.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=yongzhao.derek@gmail.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