DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Eric Kinzie <ehkinzie@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Jan Blunck <jblunck@infradead.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/bonding: validate speed after link up
Date: Wed, 5 Oct 2016 12:53:00 +0000	[thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C21A08F304@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1470335083-6380-2-git-send-email-ehkinzie@gmail.com>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Eric Kinzie
> Sent: Thursday, August 4, 2016 7:25 PM
> To: dev@dpdk.org
> Cc: Jan Blunck <jblunck@infradead.org>
> Subject: [dpdk-dev] [PATCH 1/2] net/bonding: validate speed after link up
> 
> It's possible for the bonding driver to mistakenly reject an interface based in
> it's, as yet, unnegotiated link speed and duplex.  Always allow the interface
> to be added to the bonding interface but require link properties validation to
> succeed before slave is activated.
> 
> Fixes: 2efb58cbab6e ("bond: new link bonding library")
> 
> Signed-off-by: Eric Kinzie <ehkinzie@gmail.com>

Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>

  reply	other threads:[~2016-10-05 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 18:24 [dpdk-dev] [PATCH 0/2] bonding link validation and vlan filters Eric Kinzie
2016-08-04 18:24 ` [dpdk-dev] [PATCH 1/2] net/bonding: validate speed after link up Eric Kinzie
2016-10-05 12:53   ` Iremonger, Bernard [this message]
2016-10-12 15:34     ` Bruce Richardson
2016-08-04 18:24 ` [dpdk-dev] [PATCH 2/2] net/bonding: enable slave VLAN filter Eric Kinzie
2016-10-05 12:53   ` Iremonger, Bernard
2016-09-14 14:03 ` [dpdk-dev] [PATCH 0/2] bonding link validation and vlan filters Ferruh Yigit

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=8CEF83825BEC744B83065625E567D7C21A08F304@IRSMSX108.ger.corp.intel.com \
    --to=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ehkinzie@gmail.com \
    --cc=jblunck@infradead.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).