From: Ciara Loftus <ciara.loftus@intel.com>
To: dev@dpdk.org
Cc: Ciara Loftus <ciara.loftus@intel.com>, stable@dpdk.org
Subject: [PATCH 3/8] net/iavf: fix documentation for speed capabilities
Date: Tue, 16 Sep 2025 14:21:08 +0000 [thread overview]
Message-ID: <20250916142113.3485738-4-ciara.loftus@intel.com> (raw)
In-Reply-To: <20250916142113.3485738-1-ciara.loftus@intel.com>
The iavf PMD does not report the speed capabilities that the device is
capable of in the speed_capa field of the rte_eth_dev_info struct. The
documentation incorrectly stated this feature as supported. Fix this.
Fixes: 48de41ca11f0 ("net/avf: enable link status update")
Cc: stable@dpdk.org
Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
---
doc/guides/nics/features/iavf.ini | 1 -
1 file changed, 1 deletion(-)
diff --git a/doc/guides/nics/features/iavf.ini b/doc/guides/nics/features/iavf.ini
index 61c4742197..4ce4dc5a88 100644
--- a/doc/guides/nics/features/iavf.ini
+++ b/doc/guides/nics/features/iavf.ini
@@ -7,7 +7,6 @@
; is selected.
;
[Features]
-Speed capabilities = Y
Link status = Y
Rx interrupt = Y
Queue start/stop = Y
--
2.34.1
next prev parent reply other threads:[~2025-09-16 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250916142113.3485738-1-ciara.loftus@intel.com>
2025-09-16 14:21 ` [PATCH 1/8] net/ice: document support for free Tx mbuf on demand Ciara Loftus
2025-09-16 14:21 ` [PATCH 2/8] net/ice: fix documentation of support for TSO Ciara Loftus
2025-09-16 14:21 ` Ciara Loftus [this message]
2025-09-16 14:21 ` [PATCH 4/8] net/iavf: document support for fast mbuf free Ciara Loftus
2025-09-16 14:21 ` [PATCH 5/8] net/iavf: document support for free Tx mbuf on demand Ciara Loftus
2025-09-16 14:21 ` [PATCH 6/8] net/iavf: document support for burst mode info Ciara Loftus
2025-09-16 14:21 ` [PATCH 7/8] net/iavf: fix documentation of support for TSO Ciara Loftus
2025-09-16 14:21 ` [PATCH 8/8] net/iavf: document support for extended statistics Ciara Loftus
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=20250916142113.3485738-4-ciara.loftus@intel.com \
--to=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).