From: peilinhe2020@163.com
To: he.peilin@zte.com.cn, Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: alexandre.torgue@foss.st.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, jiang.kun2@zte.com.cn,
kuba@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, vbridgers2013@gmail.com, xu.xin16@zte.com.cn
Subject: Re: [PATCH net v6] net: stmmac: remove software VLAN tag stripping
Date: Mon, 14 Sep 2026 22:38:34 +0800 [thread overview]
Message-ID: <20260914143834.5828-1-peilinhe2020@163.com> (raw)
In-Reply-To: <7d72b99f-ca65-4ad4-954c-b3f9d07de523@bootlin.com>
From: Peilin He <he.peilin@zte.com.cn>
Hi Maxime,
Thanks for the review and for the detailed debugging.
> Eaxh patch should be an independent thread, not a reply to the previous
> one.
Ack. I'll send v7 as a new series instead of a reply to the previous one.
> So this patch breaks all the stmmac selftests on some dwmac1000, e.g. on
> dwmac-meson8b :
> ...
> Can you add the following patch to your series, as patch number 1 so
> that ethtool selftests still work during bisect ? I've tested it on
> the board who'se selftest failed with this patch and it works :)
Thanks for the analysis and for testing the fix. I'll add your selftests
fix as patch 1/2, keeping your authorship, followed by the software VLAN
stripping removal as patch 2/2.
I'll send the v7 series as a new thread shortly.
Thanks,
Peilin
prev parent reply other threads:[~2026-09-14 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 0:45 [PATCH net v5] net: stmmac: remove software VLAN tag stripping he.peilin
2026-09-04 7:33 ` Maxime Chevallier
2026-09-11 14:11 ` [PATCH net v6] " peilinhe2020
2026-09-12 21:35 ` Maxime Chevallier
2026-09-14 14:38 ` peilinhe2020 [this message]
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=20260914143834.5828-1-peilinhe2020@163.com \
--to=peilinhe2020@163.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=he.peilin@zte.com.cn \
--cc=jiang.kun2@zte.com.cn \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vbridgers2013@gmail.com \
--cc=xu.xin16@zte.com.cn \
/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