From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: handle removed device properly on promisc replay
Date: Thu, 26 Sep 2019 11:43:15 +0100 [thread overview]
Message-ID: <94f3a346-3170-a2ac-51ee-37c94f4b6e72@intel.com> (raw)
In-Reply-To: <1569344480-7571-1-git-send-email-arybchenko@solarflare.com>
On 9/24/2019 6:01 PM, Andrew Rybchenko wrote:
> Promiscuous mode callback may return error if the device is removed.
> Use eth_err() helper to check the condition and return appropriate
> error code.
>
> Fixes: dff6d544fb3c ("ethdev: do nothing if promiscuous mode is applied again")
>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
Squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2019-09-26 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 17:01 Andrew Rybchenko
2019-09-26 10:43 ` Ferruh Yigit [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=94f3a346-3170-a2ac-51ee-37c94f4b6e72@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).