From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [PATCH 0/3] fix error path of multi-process probe
Date: Sat, 2 Mar 2019 03:42:50 +0100 [thread overview]
Message-ID: <20190302024253.15594-1-thomas@monjalon.net> (raw)
While working on multi-process support of failsafe with Raslan,
some issues have been discovered on probing failures.
Thomas Monjalon (3):
eal: remove useless checks for already probed device
eal: remove error logs for already probed device
eal: fix multi-process probe failure handling
lib/librte_eal/common/eal_common_dev.c | 31 ++++++++++----------------
lib/librte_eal/common/eal_private.h | 2 +-
lib/librte_eal/common/hotplug_mp.c | 14 +++++++-----
3 files changed, 21 insertions(+), 26 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-02 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 2:42 Thomas Monjalon [this message]
2019-03-02 2:42 ` [PATCH 1/3] eal: remove useless checks for already probed device Thomas Monjalon
2019-03-13 13:46 ` Zhang, Qi Z
2023-06-11 2:52 ` [dpdk-dev] " Stephen Hemminger
2019-03-02 2:42 ` [PATCH 2/3] eal: remove error logs " Thomas Monjalon
2019-03-02 2:42 ` [PATCH 3/3] eal: fix multi-process probe failure handling Thomas Monjalon
2019-03-14 7:15 ` Zhang, Qi Z
2023-06-14 19:39 ` [dpdk-dev] [PATCH 0/3] fix error path of multi-process probe Stephen Hemminger
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=20190302024253.15594-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--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 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.