From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Matan Azrad <matan@mellanox.com>
Cc: dev@dpdk.org, Ophir Munk <ophirmu@mellanox.com>, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 2/2] net/failsafe: fix duplicate event registration
Date: Tue, 22 May 2018 15:15:18 +0200 [thread overview]
Message-ID: <20180522131518.gb7e7vewtgyln2pk@bidouze.vm.6wind.com> (raw)
In-Reply-To: <1526992727-10459-2-git-send-email-matan@mellanox.com>
On Tue, May 22, 2018 at 12:38:47PM +0000, Matan Azrad wrote:
> When the fail-safe device is reconfigured, it attempts to register
> again for the sub-devices LSC and RMV events.
>
> Prevent an event registration if it is already done.
>
> Fixes: 598fb8aec6f6 ("net/failsafe: support device removal")
> Cc: stable@dpdk.org
>
> Signed-off-by: Matan Azrad <matan@mellanox.com>
Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
--
Gaëtan Rivet
6WIND
next prev parent reply other threads:[~2018-05-22 13:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 18:52 [dpdk-dev] [PATCH 1/2] net/failsafe: fix removed sub-device cleanup Matan Azrad
2018-05-17 18:52 ` [dpdk-dev] [PATCH 2/2] net/failsafe: fix duplicate event registraton Matan Azrad
2018-05-21 18:13 ` [dpdk-dev] [PATCH 1/2] net/failsafe: fix removed sub-device cleanup Ophir Munk
2018-05-21 19:48 ` [dpdk-dev] [PATCH v2 " Matan Azrad
2018-05-21 19:48 ` [dpdk-dev] [PATCH v2 2/2] net/failsafe: fix duplicate event registration Matan Azrad
2018-05-22 8:56 ` [dpdk-dev] [PATCH v2 1/2] net/failsafe: fix removed sub-device cleanup Gaëtan Rivet
2018-05-22 10:19 ` Matan Azrad
2018-05-22 11:53 ` Gaëtan Rivet
2018-05-22 12:09 ` Matan Azrad
2018-05-22 12:38 ` [dpdk-dev] [PATCH v3 " Matan Azrad
2018-05-22 12:38 ` [dpdk-dev] [PATCH v3 2/2] net/failsafe: fix duplicate event registration Matan Azrad
2018-05-22 13:15 ` Gaëtan Rivet [this message]
2018-05-22 13:14 ` [dpdk-dev] [PATCH v3 1/2] net/failsafe: fix removed sub-device cleanup Gaëtan Rivet
2018-05-22 13:59 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
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=20180522131518.gb7e7vewtgyln2pk@bidouze.vm.6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=ophirmu@mellanox.com \
--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).