From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: stable@dpdk.org, dev@dpdk.org, Jan Blunck <jblunck@infradead.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] dev: fix dev_attach proceeding with vdev on success
Date: Mon, 31 Jul 2017 09:46:39 +0200 [thread overview]
Message-ID: <1745224.TJoYg1OxSO@xps> (raw)
In-Reply-To: <3505500ec4b4a452528da1eb2076e11bdc22068c.1501069907.git.gaetan.rivet@6wind.com>
26/07/2017 13:52, Gaetan Rivet:
> When rte_eal_hotplug_add() successfully probe a device, the return value
> is zero. The check afterward only returns on error different from
> -EINVAL. It should return also on success, as there is no need to
> attempt probing the device with vdev.
>
> Fixes: 0bba9e605048 ("eal: use new hotplug API in attach")
> Cc: stable@dpdk.org
> Cc: Jan Blunck <jblunck@infradead.org>
>
> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
Applied, thanks
prev parent reply other threads:[~2017-07-31 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 11:52 [dpdk-dev] " Gaetan Rivet
2017-07-31 7:46 ` 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=1745224.TJoYg1OxSO@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=jblunck@infradead.org \
--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).