From: Simon Horman <horms@kernel.org>
To: Yibo Dong <dong100@mucse.com>
Cc: netdev-bot+sinfo@kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, vadim.fedorenko@linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
yaojun@mucse.com
Subject: Re: [PATCH net] net: rnpgbe: Accept link-down events without speed magic
Date: Wed, 28 Oct 2026 12:40:48 +0000 [thread overview]
Message-ID: <20261028124048.GR257209@horms.kernel.org> (raw)
In-Reply-To: <5A927C9600407C98+20261026092615.GA933559@nic-Precision-5820-Tower>
On Mon, Oct 26, 2026 at 05:26:15PM +0800, Yibo Dong wrote:
> On Mon, Oct 26, 2026 at 08:00:22AM +0000, netdev-bot+sinfo@kernel.org wrote:
> > Hi!
> >
> > This is an automated message. This series looks like a fix, but its
> > commit messages seem to be missing some information:
> >
> > - How the issue was discovered, e.g. hit in production, hit during
> > development, syzbot report, manual code inspection, LLM or static
> > analysis tool scan.
> >
> > - 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.
> >
> Hi,
>
> The issue was encountered during rnpgbe development and hardware
> regression testing.
>
> The fix was tested on MUCSE N210 and N500 adapters with firmware
> 1.1.8.0, using PCI passthrough to a VM. Physical N500 is used as
> link partners.
>
> With the unpatched driver, administratively bringing down the link
> partner left the VM interface reporting carrier up throughout a
> seven-second observation period. With the patch applied, the VM
> interface correctly reported carrier down.
>
> The comparison was repeated three times per adapter for both driver
> versions. After bringing the link partner back up, bidirectional
> ping passed in every case.
>
> If another revision is needed, I will include this information in
> the commit message.
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2026-10-28 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 7:54 [PATCH net] net: rnpgbe: Accept link-down events without speed magic Dong Yibo
2026-10-26 8:00 ` netdev-bot+sinfo
2026-10-26 9:26 ` Yibo Dong
2026-10-28 12:40 ` Simon Horman [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=20261028124048.GR257209@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dong100@mucse.com \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sinfo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@linux.dev \
--cc=yaojun@mucse.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