From: Stephen Hemminger <stephen@networkplumber.org>
To: Zaiyu Wang <zaiyuwang@trustnetic.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/6] net/txgbe: fill in functionality gaps for Amber-Lite NICs
Date: Fri, 24 Oct 2025 15:49:34 -0700 [thread overview]
Message-ID: <20251024154934.0ba0fd42@phoenix> (raw)
In-Reply-To: <20251023121356.21944-1-zaiyuwang@trustnetic.com>
On Thu, 23 Oct 2025 20:13:49 +0800
Zaiyu Wang <zaiyuwang@trustnetic.com> wrote:
> This patchset adds missing functionality for Amber-Lite NICs in the txgbe driver,
> addressing previously overlooked features to improve support for these devices,
> particularly for the VF.
>
> Zaiyu Wang (6):
> net/txgbe: add Amber-Lite 25G VF IDs to PCI ID map
> net/txgbe: add flush operation for Amber-Lite NICs
> net/txgbe: add RSS register selection for Amber-Lite 25G VF
> net/txgbe: add BME reset for Amber-Lite 25G VF
> net/txgbe: add check link for Amber-Lite VF
> net/txgbe: add PF-triggered VF link status change handling
>
> drivers/net/txgbe/base/txgbe_mbx.h | 2 +
> drivers/net/txgbe/base/txgbe_regs.h | 16 +++++-
> drivers/net/txgbe/base/txgbe_vf.c | 52 ++++++++++++-----
> drivers/net/txgbe/txgbe_ethdev_vf.c | 87 +++++++++++++++++++++++++++--
> 4 files changed, 136 insertions(+), 21 deletions(-)
>
Queued to next-net
prev parent reply other threads:[~2025-10-24 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 12:13 Zaiyu Wang
2025-10-23 12:13 ` [PATCH 1/6] net/txgbe: add Amber-Lite 25G VF IDs to PCI ID map Zaiyu Wang
2025-10-23 12:13 ` [PATCH 2/6] net/txgbe: add flush operation for Amber-Lite NICs Zaiyu Wang
2025-10-23 12:13 ` [PATCH 3/6] net/txgbe: add RSS register selection for Amber-Lite 25G VF Zaiyu Wang
2025-10-23 12:13 ` [PATCH 4/6] net/txgbe: add BME reset " Zaiyu Wang
2025-10-23 12:13 ` [PATCH 5/6] net/txgbe: add check link for Amber-Lite VF Zaiyu Wang
2025-10-23 12:13 ` [PATCH 6/6] net/txgbe: add PF-triggered VF link status change handling Zaiyu Wang
2025-10-24 22:49 ` Stephen Hemminger [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=20251024154934.0ba0fd42@phoenix \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=zaiyuwang@trustnetic.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;
as well as URLs for NNTP newsgroup(s).