From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Nicolau, Radu" <radu.nicolau@intel.com>,
Chas Williams <3chas3@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>,
"Charles (Chas) Williams" <ciwillia@mail.eng.vyatta.net>,
Chas Williams <chas3@att.com>
Subject: Re: [dpdk-dev] [PATCH] net/bonding: don't early mark eth device as bonded
Date: Thu, 25 Jan 2018 13:23:21 +0000 [thread overview]
Message-ID: <61e76af2-1d6e-7271-9780-addc2fa23dbf@intel.com> (raw)
In-Reply-To: <763A2F19A5EFF34F8B7F1657C992EE297B3137D3@IRSMSX104.ger.corp.intel.com>
On 1/25/2018 12:28 PM, Nicolau, Radu wrote:
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Chas Williams
>> Sent: Wednesday, January 17, 2018 4:45 PM
>> To: dev@dpdk.org
>> Cc: Doherty, Declan <declan.doherty@intel.com>; Charles (Chas) Williams
>> <ciwillia@mail.eng.vyatta.net>; Chas Williams <chas3@att.com>
>> Subject: [dpdk-dev] [PATCH] net/bonding: don't early mark eth device as
>> bonded
>>
>> From: "Charles (Chas) Williams" <ciwillia@mail.eng.vyatta.net>
>>
>> bonding immediately marks the incoming eth device as bonded and doesn't
>> clear this in later error paths. Delay marking the dev until we are certain that
>> we are going to add this eth device to the bond group.
>>
>> Signed-off-by: Chas Williams <chas3@att.com>
>> ---
>
> Acked-by: Radu Nicolau <radu.nicolau@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-01-25 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 16:44 Chas Williams
2018-01-25 12:28 ` Nicolau, Radu
2018-01-25 13:23 ` 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=61e76af2-1d6e-7271-9780-addc2fa23dbf@intel.com \
--to=ferruh.yigit@intel.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.com \
--cc=ciwillia@mail.eng.vyatta.net \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=radu.nicolau@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).