From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [PATCH] Revert "bus/vdev: fix devargs in secondary process"
Date: Mon, 17 Jun 2024 07:48:48 -0700 [thread overview]
Message-ID: <20240617074848.481d7530@hermes.local> (raw)
In-Reply-To: <20240531174118.414736-1-stephen@networkplumber.org>
On Fri, 31 May 2024 10:41:18 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> This reverts commit 6666628362c94a0b567a39a0177539c12c97d999.
>
> That commit broke use of dumpcap with vdev's and probably
> other uses of secondary processes with vdev as well.
>
> Bugzilla ID: 1450
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Please review this. Current code is broken when using vdev's
next prev parent reply other threads:[~2024-06-17 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 17:41 Stephen Hemminger
2024-06-17 14:48 ` Stephen Hemminger [this message]
2024-06-18 13:05 ` David Marchand
2024-06-19 1:38 ` Jiang, YuX
2024-06-19 15:04 ` Stephen Hemminger
2024-06-19 20:07 ` Thomas Monjalon
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=20240617074848.481d7530@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--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).