From: Stephen Hemminger <stephen@networkplumber.org>
To: Kaisen You <kaisenx.you@intel.com>
Cc: dev@dpdk.org, qiming.yang@intel.com, yidingx.zhou@intel.com,
stable@dpdk.org
Subject: Re: [PATCH] app/test:add NIC parameter exception handling
Date: Thu, 13 Jun 2024 08:30:33 -0700 [thread overview]
Message-ID: <20240613083033.605a1d20@hermes.local> (raw)
In-Reply-To: <20230713051716.2579821-1-kaisenx.you@intel.com>
On Thu, 13 Jul 2023 13:17:16 +0800
Kaisen You <kaisenx.you@intel.com> wrote:
> Add NIC exception parameter handling to dpdk_test process,
> program exits when carrying unbound vfio NIC parameters.
>
> Fixes: 50247fe03fe0 ("test/timer: exercise new APIs in secondary process")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kaisen You <kaisenx.you@intel.com>
> ---
I don't think covering up a configuration problem is good idea.
What causes this, why should it be fixed here and not in the test setup.
prev parent reply other threads:[~2024-06-13 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 5:17 Kaisen You
2024-06-13 15:30 ` 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=20240613083033.605a1d20@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=kaisenx.you@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=yidingx.zhou@intel.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).