From: David Miller <davem@davemloft.net>
To: jtoppins@cumulusnetworks.com
Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] bonding: various 802.3ad fixes
Date: Tue, 27 Jan 2015 17:09:27 -0800 (PST) [thread overview]
Message-ID: <20150127.170927.1945702034995194886.davem@davemloft.net> (raw)
In-Reply-To: <1422253021-3798-1-git-send-email-jtoppins@cumulusnetworks.com>
From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
Date: Mon, 26 Jan 2015 01:16:56 -0500
> This patch series is a forward porting of patches we (Cumulus) are shipping
> in our 3.2 series kernels. These fixes attempt to make 802.3ad bonding mode
> more predictable in certian state machine transtions in addition to fixing
> 802.3ad bond carrier determination when bonding min_links option is changed.
> Specific notes are contained within each patch.
>
> For this patch series there are no userspace facing changes, a diff between
> the modinfo output showed no difference. However, there are behavioral
> facing changes, primarily in the bond carrier state. Please make sure to
> review carefully.
>
> v2:
> * fixed some style issues
> * dropped a portion of patch 1 in favor of more testing on my side
Series applied, thanks.
prev parent reply other threads:[~2015-01-28 1:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 6:16 [PATCH net-next v2 0/5] bonding: various 802.3ad fixes Jonathan Toppins
2015-01-26 6:16 ` [PATCH net-next v2 1/5] bonding: update bond carrier state when min_links option changes Jonathan Toppins
2015-01-27 0:29 ` Jay Vosburgh
2015-01-26 6:16 ` [PATCH net-next v2 2/5] bonding: fix bond_open() don't always set slave active flag Jonathan Toppins
2015-01-27 0:33 ` Jay Vosburgh
2015-01-26 6:16 ` [PATCH net-next v2 3/5] bonding: fix incorrect lacp mux state when agg not active Jonathan Toppins
2015-01-27 2:42 ` Jay Vosburgh
2015-01-26 6:17 ` [PATCH net-next v2 4/5] bonding: fix LACP PDU not sent on slave port sometimes Jonathan Toppins
2015-01-26 12:04 ` Sergei Shtylyov
2015-01-27 0:45 ` Jay Vosburgh
2015-01-26 6:17 ` [PATCH net-next v2 5/5] bonding: cleanup and remove dead code Jonathan Toppins
2015-01-27 0:46 ` Jay Vosburgh
2015-01-27 0:49 ` [PATCH net-next v2 0/5] bonding: various 802.3ad fixes Andy Gospodarek
2015-01-28 1:09 ` David Miller [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=20150127.170927.1945702034995194886.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=j.vosburgh@gmail.com \
--cc=jtoppins@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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).