From: Stephen Hemminger <stephen@networkplumber.org>
To: Navin Srinivas <g.navinsrinivas@gmail.com>
Cc: bugzilla@dpdk.org, dev@dpdk.org
Subject: Re: [DPDK/other Bug 1562] dumpcap captures all available network interfaces when specifying any PCI network interface
Date: Wed, 12 Feb 2025 07:02:34 -0800 [thread overview]
Message-ID: <20250212070234.7f69425e@hermes.local> (raw)
In-Reply-To: <CACOt6jyPUfBPaX7t4rYde8dTgn9-we38s7WYFrrYx0iOyOC7FQ@mail.gmail.com>
On Wed, 12 Feb 2025 13:29:57 +0530
Navin Srinivas <g.navinsrinivas@gmail.com> wrote:
> Hi,
>
> Is this backported to 22.11.1?
>
> Thanks,
> Navn Srinivas
No, it required a couple of other patches related to management of network interface list.
prev parent reply other threads:[~2025-02-12 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 2:23 bugzilla
2024-10-24 9:02 ` bugzilla
2025-02-12 7:59 ` Navin Srinivas
2025-02-12 15:02 ` 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=20250212070234.7f69425e@hermes.local \
--to=stephen@networkplumber.org \
--cc=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
--cc=g.navinsrinivas@gmail.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).