From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Gary Mussar <gmussar@ciena.com>, "dev@dpdk.org" <dev@dpdk.org>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] Tools: Fix issue with virtio interface names
Date: Fri, 23 Sep 2016 17:49:36 +0800 [thread overview]
Message-ID: <20160923094936.GE23158@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2025F07D6@IRSMSX103.ger.corp.intel.com>
On Fri, Sep 02, 2016 at 03:23:34PM +0000, Mcnamara, John wrote:
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gary Mussar
> > Sent: Friday, September 2, 2016 2:17 PM
> > To: dev@dpdk.org
> > Cc: Gary Mussar <gmussar@ciena.com>
> > Subject: [dpdk-dev] [PATCH] Tools: Fix issue with virtio interface names
> >
> > The dpdk-devbind.py script does not find/display the ifname for virtio
> > interfaces since the "net" directory is not directly under the device
> > directory but rather under a subdirectory.
> > eg.
> > > dpdk-devbind.py --status
> > 0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=
> >
> > This change searches for the first "net" directory under the device
> > directory hierarchy.
> > eg.
> > 0000:00:03.0 'Virtio network device' if=ens3 drv=virtio-pci unused=
> >
> > Fixes: 629395b063e8 ("igb_uio: remove PCI id table")
> >
> > Signed-off-by: Gary Mussar <gmussar@ciena.com>
>
> Thanks for that.
>
> Note, the subject line should be lowercase but apart from that:
Applied to dpdk-next-virtio, this this minor fix.
And, it looks like a good candidate for stable release, so,
stable@dpdk.org cc'ed.
Thanks.
--yliu
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
>
parent reply other threads:[~2016-09-23 9:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <B27915DBBA3421428155699D51E4CFE2025F07D6@IRSMSX103.ger.corp.intel.com>]
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=20160923094936.GE23158@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=gmussar@ciena.com \
--cc=john.mcnamara@intel.com \
--cc=stable@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).