From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Chas Williams <3chas3@gmail.com>, dev@dpdk.org
Cc: Chas Williams <chas3@att.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/bonding: fix invalid link status
Date: Mon, 18 Feb 2019 16:21:29 +0000 [thread overview]
Message-ID: <4cc3485c-37e1-92ba-0c5c-ff99b360f569@intel.com> (raw)
In-Reply-To: <20190214191112.31018-1-3chas3@gmail.com>
On 2/14/2019 7:11 PM, Chas Williams wrote:
> From: Chas Williams <chas3@att.com>
>
> Copying the link properties of the first slave added may copy an
> invalid link status. The speed and duplex of the slave may not
> be known at this time. Delay setting the properties until the
> first slave reports as link up. Note that we are still ignoring
> an error from link_properties_valid. For some bonding modes,
> 802.3ad, we should not activate the slave if it does not have
> matching link properties.
>
> Fixes: a45b288ef21a ("bond: support link status polling")
> Cc: stable@dpdk.org
> Signed-off-by: Chas Williams <chas3@att.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-02-18 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 19:11 Chas Williams
2019-02-18 16:21 ` 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=4cc3485c-37e1-92ba-0c5c-ff99b360f569@intel.com \
--to=ferruh.yigit@intel.com \
--cc=3chas3@gmail.com \
--cc=chas3@att.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).