From: "Zaiyu Wang" <zaiyuwang@trustnetic.com>
To: "'Stephen Hemminger'" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH 00/13] Wangxun fixes and new features
Date: Tue, 8 Sep 2026 20:43:43 +0800 [thread overview]
Message-ID: <000a01dd3f8f$aeeb6ac0$0cc24040$@trustnetic.com> (raw)
In-Reply-To: <20260827131137.1daf141c@phoenix.local>
Hi Stephen,
Thank you very much for the detailed review and for taking the time to go through each patch carefully.
I have evaluated every comment and addressed them in v2. The points that are not changed in this revision are explained in the cover letter.
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Friday, August 28, 2026 4:12 AM
> To: Zaiyu Wang <zaiyuwang@trustnetic.com>; Zaiyu Wang <zaiyuwang@trustnetic.com>
> Cc: dev@dpdk.org; dev@dpdk.org
> Subject: Re: [PATCH 00/13] Wangxun fixes and new features
>
> On Thu, 27 Aug 2026 19:41:52 +0800
> Zaiyu Wang <zaiyuwang@trustnetic.com> wrote:
>
> > This series addresses link-related issues on Wangxun Amber-lite 25G/40G NICs (CR/KR training, hot-plug, 10G link state), and additionally
> refines UDP offload handling.
>
>
> Using Claude AI review (versus the simpler CI AI review) shows several issues that need addressing before this can be merged.
>
> Here is my edit of the wordy AI feedbac.
>
prev parent reply other threads:[~2026-09-08 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 11:41 [PATCH 00/13] Wangxun fixes and new features Zaiyu Wang
2026-08-27 20:11 ` Stephen Hemminger
2026-09-08 12:43 ` Zaiyu Wang [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='000a01dd3f8f$aeeb6ac0$0cc24040$@trustnetic.com' \
--to=zaiyuwang@trustnetic.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.