From: Jay Vosburgh <fubar@us.ibm.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: [PATCH net-next-2.6 0/4] bonding: Four patches
Date: Fri, 28 Aug 2009 14:57:48 -0700 [thread overview]
Message-ID: <1251496672-14498-1-git-send-email-fubar@us.ibm.com> (raw)
Four patches for bonding:
Patch 1 adds the propogation of vlan_features from the slaves
to the master device.
Patch 2 replaces a cumbersome manual MAC address comparison with
compare_ether_addr.
Patch 3 removes a useless test against INT_MAX.
Patch 4 modifies bond_check_dev_link to handle devices that leave
carrier up even when adminstratively down.
Due to lab machine adventures on my end, I was only able to compile
test patches 2 - 4.
Please apply for net-next-2.6.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next reply other threads:[~2009-08-28 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 21:57 Jay Vosburgh [this message]
2009-08-28 21:57 ` [PATCH] bonding: propogate vlan_features to bonding master Jay Vosburgh
2009-08-28 21:57 ` [PATCH] bonding: use compare_ether_addr Jay Vosburgh
2009-08-28 21:57 ` [PATCH] Fix useless test: int > INT_MAX Jay Vosburgh
2009-08-28 21:57 ` [PATCH] From: Petri Gynther <pgynther@google.com> Jay Vosburgh
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=1251496672-14498-1-git-send-email-fubar@us.ibm.com \
--to=fubar@us.ibm.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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