From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Wei Ling <weix.ling@intel.com>
Subject: Re: [dpdk-dev] [PATCH] usertools/dpdk-devbind: fix missing device classes
Date: Tue, 24 Nov 2020 09:53:02 -0800 [thread overview]
Message-ID: <20201124095302.46c53dbf@hermes.local> (raw)
In-Reply-To: <20201124094656.46507-1-bruce.richardson@intel.com>
On Tue, 24 Nov 2020 09:46:56 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:
> The "misc" and "regex" device classes were missing from the list used to
> check arguments, preventing them from being used with "--status-dev"
> flag to list only devices of those types.
>
> When adding them to the list, the list is also sorted alphabetically for
> consistency.
>
> Fixes: 81255f27c65c ("usertools: replace optparse with argparse")
> Cc: stephen@networkplumber.org
>
> Bugzilla ID: 582
>
> Reported-by: Wei Ling <weix.ling@intel.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Almost the same patch I was sending right now...
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2020-11-24 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 8:51 [dpdk-dev] [Bug 582] [Regression Test] usertools/dpdk-devbind.py: execute "./usertools/dpdk-devbind.py --status-dev misc" command to get CBDMA device info failed bugzilla
2020-11-24 9:46 ` [dpdk-dev] [PATCH] usertools/dpdk-devbind: fix missing device classes Bruce Richardson
2020-11-24 17:53 ` Stephen Hemminger [this message]
2020-11-25 2:23 ` Jiang, YuX
2020-11-25 13:04 ` Thomas Monjalon
2020-11-25 13:06 ` Thomas Monjalon
2020-11-25 2:28 ` [dpdk-dev] [Bug 582] [dpdk-20.11] usertools/dpdk-devbind.py "misc" option no longer available bugzilla
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=20201124095302.46c53dbf@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=weix.ling@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.