From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
"Varghese, Vipin" <vipin.varghese@intel.com>
Cc: dev <dev@dpdk.org>, "Patel, Amol" <amol.patel@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/tap: invoke probe finish for multiq failure
Date: Wed, 7 Nov 2018 19:03:56 +0000 [thread overview]
Message-ID: <04371119-40bc-1265-4181-8b7f11500c49@intel.com> (raw)
In-Reply-To: <4BCFFA6A-1160-484E-955A-F8A9E683B308@intel.com>
On 11/7/2018 3:11 PM, Wiles, Keith wrote:
>
>
>> On Nov 7, 2018, at 1:58 PM, Varghese, Vipin <vipin.varghese@intel.com> wrote:
>>
>> In scenarion for multiq or flowq setup failure rte_eth_dev_probing_finish
>> has to be invoked for successful device registration.
>>
>>
>> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
>
> Acked-by: Keith Wiles <keith.wiles@intel.com>
Fixes: fbe90cdd776c ("ethdev: add probing finish function")
Cc: stable@dpdk.org
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-11-07 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 13:58 Vipin Varghese
2018-11-07 15:11 ` Wiles, Keith
2018-11-07 19:03 ` 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=04371119-40bc-1265-4181-8b7f11500c49@intel.com \
--to=ferruh.yigit@intel.com \
--cc=amol.patel@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=vipin.varghese@intel.com \
/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).