From: netdev-bot+sinfo@kernel.org
To: memoriaru@foxmail.com
Cc: netdev@vger.kernel.org, daniel.machon@microchip.com,
Steen.Hegelund@microchip.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net v4 1/2] net: sparx5: fix RX ring stall on frames from inactive ports
Date: Fri, 13 Nov 2026 12:27:42 +0000 [thread overview]
Message-ID: <179457286256.2168702.18264934758853091645@kernel.org> (raw)
In-Reply-To: <tencent_76692FA5A375ED2DD8652E064B0A6BA09007@qq.com>
Hi!
This is an automated message. This series looks like a fix, but its
commit messages seem to be missing some information:
- What hardware the change was tested on. For driver fixes please
mention the device (and if relevant firmware version) used for
testing, or say that the change was not tested on real hardware.
Please do not repost the series just to address the above. Instead,
reply to this email with the missing information, so that reviewers
can take it into account. If the series needs another revision for
other reasons, please include the information in the commit messages
then.
The evaluation is done by an LLM so it may be wrong, if you think
that is the case please reply and explain.
next prev parent reply other threads:[~2026-11-13 12:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261109164100.8947-1-memoriaru@foxmail.com>
2026-11-09 16:40 ` [PATCH net v3 1/2] net: sparx5: fix RX ring stall on frames from inactive ports memoriaru
2026-11-09 16:41 ` [PATCH net v3 2/2] net: lan969x: " memoriaru
2026-11-10 10:52 ` Daniel Machon
2026-11-13 12:24 ` [PATCH net v4 0/2] net: sparx5/lan969x: " memoriaru
[not found] ` <20261113122439.26292-1-memoriaru@foxmail.com>
2026-11-13 12:24 ` [PATCH net v4 1/2] net: sparx5: " memoriaru
2026-11-13 12:27 ` netdev-bot+sinfo [this message]
2026-11-13 12:24 ` [PATCH net v4 2/2] net: lan969x: " memoriaru
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=179457286256.2168702.18264934758853091645@kernel.org \
--to=netdev-bot+sinfo@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=memoriaru@foxmail.com \
--cc=netdev@vger.kernel.org \
/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