From: hailinxx <hailinx.xu@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, rajesh.t.puttaswamy@intel.com,
john.mcnamara@intel.com, hailinxx <hailinx.xu@intel.com>
Subject: [PATCH v1 0/2] updated latest recommended matching list
Date: Mon, 24 Nov 2025 08:50:08 +0000 [thread overview]
Message-ID: <20251124085010.707091-1-hailinx.xu@intel.com> (raw)
1. Remove recommended versions before 21.11
2. Update 25.11 recommended matching list
Hailin Xu (2):
net/ice: updated latest recommended matching list
net/i40e: updated latest recommended matching list
doc/guides/nics/i40e.rst | 72 +++-------------------------------------
doc/guides/nics/ice.rst | 13 +++-----
2 files changed, 8 insertions(+), 77 deletions(-)
--
2.34.1
next reply other threads:[~2025-11-24 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 8:50 hailinxx [this message]
2025-11-24 8:50 ` [PATCH v1 1/2] net/ice: " hailinxx
2025-11-24 8:50 ` [PATCH v1 2/2] net/i40e: " hailinxx
2025-11-24 12:18 ` [PATCH v1 0/2] " Bruce Richardson
2025-11-24 12:20 ` Bruce Richardson
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=20251124085010.707091-1-hailinx.xu@intel.com \
--to=hailinx.xu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=rajesh.t.puttaswamy@intel.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).