DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] usertools: add status-dev argument to devbind
Date: Sun, 30 Apr 2017 14:45:56 +0200	[thread overview]
Message-ID: <3801726.CAdj7BrfdN@xps> (raw)
In-Reply-To: <20170427175537.26147-1-ferruh.yigit@intel.com>

27/04/2017 19:55, Ferruh Yigit:
> Script displays status for all device types and output is much
> longer than it used to be. This makes harder to read script output.
> 
> This patch adds new --status-dev argument to the script to select
> a device group to display status.
> 
> Supported device groups:
> net
> crypto
> event
> mempool
> 
> Sample usage:
> ./usertools/dpdk-devbind.py --status-dev mempool
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied, thanks

      reply	other threads:[~2017-04-30 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 11:58 [dpdk-dev] [PATCH] usertools: reduce devbind status output Ferruh Yigit
2017-04-26 13:09 ` Thomas Monjalon
2017-04-27 17:55 ` [dpdk-dev] [PATCH v2] usertools: add status-dev argument to devbind Ferruh Yigit
2017-04-30 12:45   ` Thomas Monjalon [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=3801726.CAdj7BrfdN@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).