From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
Alejandro Lucero <alejandro.lucero@netronome.com>,
dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] ethdev: fix error handling logic
Date: Tue, 25 Sep 2018 15:12:11 +0100 [thread overview]
Message-ID: <42e3ed7a-09ca-bd23-b16f-d0c6899763f3@intel.com> (raw)
In-Reply-To: <7a20a3f2-bf64-31d8-1ced-b92fcd204f30@solarflare.com>
On 9/24/2018 3:10 PM, Andrew Rybchenko wrote:
> On 9/24/18 4:43 PM, Alejandro Lucero wrote:
>> This patch fixes how function exit is handled when errors inside
>> rte_eth_dev_create.
>>
>> Fixes: e489007a411c ("ethdev: add generic create/destroy ethdev APIs")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
>
> Minor nit/observation below, but anyway
>
> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-09-25 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 13:43 [dpdk-stable] " Alejandro Lucero
2018-09-24 14:10 ` [dpdk-stable] [dpdk-dev] " Andrew Rybchenko
2018-09-25 14:12 ` 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=42e3ed7a-09ca-bd23-b16f-d0c6899763f3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--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).