From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1562] dumpcap captures all available network interfaces when specifying any PCI network interface
Date: Thu, 24 Oct 2024 09:02:40 +0000 [thread overview]
Message-ID: <bug-1562-3-P2fNaCPFLO@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1562-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1562
Kevin Traynor (ktraynor@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Kevin Traynor (ktraynor@redhat.com) ---
Thanks for reporting. It is fixed in main branch, but Stephen says it is not
worth to backport to older releases. If it is important for you and you want to
send a patch for 22.11 and 23.11 branches, it could be accepted.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2846 bytes --]
prev parent reply other threads:[~2024-10-24 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 2:23 bugzilla
2024-10-24 9:02 ` 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-1562-3-P2fNaCPFLO@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;
as well as URLs for NNTP newsgroup(s).