From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Gaëtan Rivet" <gaetan.rivet@6wind.com>,
"Andrew Rybchenko" <arybchenko@solarflare.com>
Cc: dev@dpdk.org, Igor Romanov <Igor.Romanov@oktetlabs.ru>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2] net/failsafe: report actual device capabilities
Date: Mon, 1 Oct 2018 15:38:39 +0100 [thread overview]
Message-ID: <0448786a-eae0-6ec9-72fd-32796a718a1b@intel.com> (raw)
In-Reply-To: <20180926115815.rlwzryfognltlzq5@bidouze.vm.6wind.com>
On 9/26/2018 12:58 PM, Gaëtan Rivet wrote:
> On Wed, Sep 26, 2018 at 07:38:04AM +0100, Andrew Rybchenko wrote:
>> From: Igor Romanov <Igor.Romanov@oktetlabs.ru>
>>
>> Failsafe device capabilities depend on supported by the failsafe
>> itself plus capabilities supported by sub-devices.
>> Make fs_dev_infos_get() take failsafe device capabilities into account.
>>
>> Fixes: cac923cfea47 ("ethdev: support runtime queue setup")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Igor Romanov <Igor.Romanov@oktetlabs.ru>
>> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
>
> Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-10-01 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 7:45 [dpdk-stable] [PATCH] net/failsafe: limit device capabilities to really supported Andrew Rybchenko
2018-09-25 15:48 ` Gaëtan Rivet
2018-09-26 6:36 ` [dpdk-stable] [dpdk-dev] " Andrew Rybchenko
2018-09-26 6:38 ` [dpdk-stable] [PATCH v2] net/failsafe: report actual device capabilities Andrew Rybchenko
2018-09-26 11:58 ` Gaëtan Rivet
2018-10-01 14:38 ` 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=0448786a-eae0-6ec9-72fd-32796a718a1b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Igor.Romanov@oktetlabs.ru \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.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).