From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Jan Blunck <jblunck@infradead.org>,
Gaetan Rivet <gaetan.rivet@6wind.com>,
Tetsuya Mukawa <mtetsuyah@gmail.com>,
Declan Doherty <declan.doherty@intel.com>
Subject: Re: [PATCH] eal: remove vdev probe by dev args
Date: Mon, 10 Jul 2017 00:02:34 +0200 [thread overview]
Message-ID: <1877200.0P2trkeMB8@xps> (raw)
In-Reply-To: <CALe+Z01fT1+OdkOBMixKOOyuS7oE6=XL1fR5Agm=Hf=p70FupQ@mail.gmail.com>
09/07/2017 09:54, Jan Blunck:
> On Fri, Jun 16, 2017 at 10:20 AM, Thomas Monjalon <thomas@monjalon.net> wrote:
> > Please Jan, could you comment?
> >
>
> My intention was to provide a way that devices can have arbitrary
> names. Ferruh correctly pointed out that this is undocumented and
> hidden functionality. Lets apply this and I can rework this if it
> becomes necessary later.
>
> > 09/06/2017 11:21, Ferruh Yigit:
> >> On 6/8/2017 9:45 PM, Thomas Monjalon wrote:
> >> > 10/05/2017 13:01, Ferruh Yigit:
> >> >> Virtual device/driver probing done via name.
> >> >>
> >> >> A new alternative method introduced to probe the device with providing
> >> >> driver name in devargs as "driver=<driver_name>".
> >> >>
> >> >> This patch removes alternative method and fixes virtual device usages
> >> >> with proper device names.
> >> >>
> >> >> Fixes: 87c3bf29c642 ("test: do not short-circuit null device creation")
> >> >> Fixes: d39670086a63 ("eal: parse driver argument before probing drivers")
> >> >>
> >> >> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied
prev parent reply other threads:[~2017-07-09 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 11:01 [PATCH] eal: remove vdev probe by dev args Ferruh Yigit
2017-06-08 20:45 ` Thomas Monjalon
2017-06-09 9:21 ` Ferruh Yigit
2017-06-16 14:20 ` Thomas Monjalon
2017-07-09 7:54 ` Jan Blunck
2017-07-09 22:02 ` 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=1877200.0P2trkeMB8@xps \
--to=thomas@monjalon.net \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=jblunck@infradead.org \
--cc=mtetsuyah@gmail.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.