From: Thomas Monjalon <thomas@monjalon.net>
To: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pci: propagate exact error codes in pci_probe_all_drivers()
Date: Mon, 29 Oct 2018 01:57:15 +0100 [thread overview]
Message-ID: <4943602.Wu5sgN3NIT@xps> (raw)
In-Reply-To: <20181026075459.21637-1-dariusz.stojaczyk@intel.com>
26/10/2018 09:54, Darek Stojaczyk:
> In a couple of places we check its error code against -EEXIST,
> but this function returned either -1, 0, or 1.
>
> This gets critical when hotplugging a device in secondary
> process, while the same device is already plugged in the
> primary. Failing to "hotplug" it in the primary will cause
> the secondary to fail as well.
>
> Fixes: e9d159c3d534 ("eal: allow probing a device again")
> Cc: thomas@monjalon.net
> Cc: stable@dpdk.org
No need of Cc: stable here.
> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks
prev parent reply other threads:[~2018-10-29 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 7:54 Darek Stojaczyk
2018-10-29 0:57 ` 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=4943602.Wu5sgN3NIT@xps \
--to=thomas@monjalon.net \
--cc=dariusz.stojaczyk@intel.com \
--cc=dev@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).