patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Radu Nicolau <radu.nicolau@intel.com>,
	Chas Williams <3chas3@gmail.com>,
	dev@dpdk.org
Cc: declan.doherty@intel.com,
	"Charles (Chas) Williams" <chas3@att.com>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] net/bonding: clear dev_started if start fails
Date: Fri, 6 Apr 2018 11:03:21 +0100	[thread overview]
Message-ID: <ef0f4cbf-180a-fe30-c441-9a23d15c0439@intel.com> (raw)
In-Reply-To: <d989c26b-2984-f1cb-b2d8-6d232c6a7fb5@intel.com>

On 4/5/2018 11:58 AM, Radu Nicolau wrote:
> 
> 
> On 3/23/2018 5:05 PM, Chas Williams wrote:
>> From: "Charles (Chas) Williams" <chas3@att.com>
>>
>> There are several error paths where the bonding device may not start.
>> Clear dev_started before we return if we take one of these paths.
>>
>> Fixes: 2efb58cbab ("bond: new link bonding library")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Chas Williams <chas3@att.com>
>> ---
>>
> Acked-by: Radu Nicolau <radu.nicolau@intel.com> 

Applied to dpdk-next-net/master, thanks.

  reply	other threads:[~2018-04-06 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 16:34 [dpdk-stable] [PATCH] net/bonding: set dev_started later Chas Williams
2018-03-23 17:05 ` [dpdk-stable] [PATCH v2] net/bonding: clear dev_started if start fails Chas Williams
2018-04-05 10:58   ` [dpdk-stable] [dpdk-dev] " Radu Nicolau
2018-04-06 10:03     ` Ferruh Yigit [this message]
2018-06-14 17:10 ` [dpdk-stable] [dpdk-dev] [PATCH] net/bonding: set dev_started later Ferruh Yigit
2018-06-14 20:22   ` Chas Williams

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=ef0f4cbf-180a-fe30-c441-9a23d15c0439@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=3chas3@gmail.com \
    --cc=chas3@att.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=radu.nicolau@intel.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).