netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, vfalico@gmail.com,
	gospo@cumulusnetworks.com, shm@cumulusnetworks.com,
	razor@blackwall.org
Subject: Re: [PATCH linux v3 net-next 0/5] add netlink support for new lacp bonding parameters
Date: Mon, 11 May 2015 11:50:20 -0400	[thread overview]
Message-ID: <5550CFBC.9050805@cumulusnetworks.com> (raw)
In-Reply-To: <20150511.110004.649964826481502303.davem@davemloft.net>

On 5/11/15 11:00 AM, David Miller wrote:
> From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
> Date: Sat,  9 May 2015 00:01:54 -0700
>
>> This is a resubmit of Mahesh's last 3 bonding patches from this series
>> (http://marc.info/?l=linux-netdev&m=142432864626179&w=2) with one
>> additional kernel patch which adds the netlink bits. I have noted any
>> modifications I did to the original patches just above my signoff line.
>> Patch 5 is the iproute2 support for these bonding options. All patches
>> were coded against the net-next branch of their respective projects.
>>
>> v2:
>>    * rebased
>>    * only send these new parameters via netlink when bond is in mode 4
>>    * fixed ad_actor_sys_prio to be 0xFFFF by default even when the bond
>>      is initially created in mode 0 and switched to mode 4
>>
>> v3:
>>    * reverted changes to bond_option_ad_actor_system_set() from v1 in Mahesh's
>>      patch "bonding: Allow userspace to set actors' macaddr in an AD-system."
>>      Instead implementing all setting in the option specific set function as
>>      Nik suggested.
>
> Series applied, thanks.
>
> There are actually 4 patches in this series, so this subject should have
> said "0/4" instead of "0/5" :-)
>

Thanks David, noted for next time, apologies for confusion.

      reply	other threads:[~2015-05-11 15:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09  7:01 [PATCH linux v3 net-next 0/5] add netlink support for new lacp bonding parameters Jonathan Toppins
2015-05-09  7:01 ` [PATCH linux v3 net-next 1/4] bonding: Allow userspace to set actors' system_priority in AD system Jonathan Toppins
2015-05-09  7:01 ` [PATCH linux v3 net-next 2/4] bonding: Allow userspace to set actors' macaddr in an AD-system Jonathan Toppins
2015-05-09  7:01 ` [PATCH linux v3 net-next 3/4] bonding: Implement user key part of port_key in an AD system Jonathan Toppins
2015-05-09  7:01 ` [PATCH linux v3 net-next 4/4] bonding: add netlink support for sys prio, actor sys mac, and port key Jonathan Toppins
2015-05-10  7:54   ` Nikolay Aleksandrov
2015-05-09  7:01 ` [PATCH iproute2 v3 net-next] iplink_bond: add support for ad_actor and port_key options Jonathan Toppins
2015-05-21 22:27   ` Stephen Hemminger
2015-05-11 15:00 ` [PATCH linux v3 net-next 0/5] add netlink support for new lacp bonding parameters David Miller
2015-05-11 15:50   ` Jonathan Toppins [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=5550CFBC.9050805@cumulusnetworks.com \
    --to=jtoppins@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=gospo@cumulusnetworks.com \
    --cc=j.vosburgh@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=razor@blackwall.org \
    --cc=shm@cumulusnetworks.com \
    --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).