From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Cc: john.mcnamara@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] devbind: check for lspci
Date: Tue, 13 Nov 2018 16:03:49 +0000 [thread overview]
Message-ID: <b757d0b2-8b9d-fa24-1f16-4338ec86c2e9@intel.com> (raw)
In-Reply-To: <e6f3dbb8-8cea-515e-e872-50be49edd3d0@intel.com>
On 07-Nov-18 4:01 PM, Ferruh Yigit wrote:
> On 11/7/2018 1:56 PM, Anatoly Burakov wrote:
>> On some distributions (such as CentOS 7) lspci may not be installed
>> by default, causing exceptions which are difficult to interpret.
>>
>> Fix devbind script to check if lspci is installed at script startup.
>
> I guess we need lspci for `--status`, bind/unbind can be done without `lspci`,
> what about adding check only display path?
This is actually incorrect. While we *use* the lspci output only on
display paths, we actually gather info about devices using lspci in
get_device_details(). So, i'll leave the code as is and just fix the
package name for v2.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-11-13 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 13:56 [dpdk-dev] " Anatoly Burakov
2018-11-07 16:01 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2018-11-07 16:30 ` Burakov, Anatoly
2018-11-07 18:07 ` Ferruh Yigit
2018-11-08 20:38 ` Rami Rosen
2018-11-09 12:03 ` Burakov, Anatoly
2018-11-10 11:03 ` Rami Rosen
2018-11-12 9:18 ` Burakov, Anatoly
2018-11-13 16:03 ` Burakov, Anatoly [this message]
2018-11-13 16:06 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2018-11-16 16:54 ` Rami Rosen
2018-11-18 23:05 ` 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=b757d0b2-8b9d-fa24-1f16-4338ec86c2e9@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).