From: Jan Viktorin <viktorin@rehivetech.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, david.marchand@6wind.com
Subject: Re: [dpdk-dev] [PATCH] app/test: remove rte_pci_dev_ids.h from pci_autotest
Date: Wed, 15 Jun 2016 11:51:40 +0200 [thread overview]
Message-ID: <20160615115140.7b6f781a@pcviktorin.fit.vutbr.cz> (raw)
In-Reply-To: <3619975.NzbGfMYzOD@xps13>
On Tue, 14 Jun 2016 16:08:42 +0200
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> 2016-06-14 15:46, Jan Viktorin:
> > There are 2 new fake devices for testing PCI infra. All the fake devices
s/All the fake/All 3 fake/
> > are now identified by non-existing vendor and device IDs so there is no
> > real driver to bind to them. The testing drivers match those IDs.
>
> Why not removing the existing sysfs entries faking real devices?
There is no reason to remove anything. All 3 devices are fakes. The original
one was changed to have fake IDs.
Is it more clear now?
Jan
> Thanks
next prev parent reply other threads:[~2016-06-15 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 13:46 Jan Viktorin
2016-06-14 14:08 ` Thomas Monjalon
2016-06-15 9:51 ` Jan Viktorin [this message]
2016-06-15 13:54 ` 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=20160615115140.7b6f781a@pcviktorin.fit.vutbr.cz \
--to=viktorin@rehivetech.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).