From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1699] Bonding device documentation missing
Date: Sat, 24 Jan 2026 20:23:10 +0000 [thread overview]
Message-ID: <bug-1699-3-0zlAM2rw1c@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1699-3@http.bugs.dpdk.org/>
http://bugs.dpdk.org/show_bug.cgi?id=1699
Stephen Hemminger (stephen@networkplumber.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Stephen Hemminger (stephen@networkplumber.org) ---
This NIC was dropped from table intentionally by:
commit 7b103c4ccd98e3f3d457c74960acd28dac64392d
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Thu Mar 12 00:01:35 2020 +0100
doc: remove empty columns from NIC features matrix
The virtual PMDs bonding, KNI, null, ring, softnic and vdev_netvsc
have no real feature to advertise so they can be removed
from the (too) big matrix of ethdev features.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-01-24 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 16:28 [DPDK/ethdev Bug 1699] Bonding device documentation missing bugzilla
2026-01-24 20:23 ` bugzilla [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=bug-1699-3-0zlAM2rw1c@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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