From: Nikolay Aleksandrov <nikolay@redhat.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, andy@greyhouse.net, fubar@us.ibm.com
Subject: [PATCH net-next 0/3] bonding: struct bonding cleanup and MAC set fixes
Date: Wed, 26 Jun 2013 17:13:36 +0200 [thread overview]
Message-ID: <1372259619-32430-1-git-send-email-nikolay@redhat.com> (raw)
Hello,
This patchset removes some unnecessary struct bonding members. It also
fixes MAC setting inconsistencies (i.e. if a bond's MAC is set after
creation but prior to enslaving, it is lost and the first slave's MAC is
cloned again). Before these patches the only way to keep a user-defined MAC
is either to set it after enslaving or to create the bond with that MAC.
Patch 01 - removes setup_by_slave member
Patch 02 - removes dev_addr_from_first member and does the MAC fixing
Patch 03 - introduces the use of NET_ADDR_STOLEN when a MAC is cloned
Best regards,
Nikolay Aleksandrov
Nikolay Aleksandrov (3):
bonding: remove unnecessary setup_by_slave member
bonding: remove unnecessary dev_addr_from_first member
bonding: when cloning a MAC use NET_ADDR_STOLEN
drivers/net/bonding/bond_main.c | 45 ++++++++++++++++++++---------------------
drivers/net/bonding/bonding.h | 2 --
2 files changed, 22 insertions(+), 25 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-06-26 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 15:13 Nikolay Aleksandrov [this message]
2013-06-26 15:13 ` [PATCH net-next 1/3] bonding: remove unnecessary setup_by_slave member Nikolay Aleksandrov
2013-06-26 15:13 ` [PATCH net-next 2/3] bonding: remove unnecessary dev_addr_from_first member Nikolay Aleksandrov
2013-06-26 15:13 ` [PATCH net-next 3/3] bonding: when cloning a MAC use NET_ADDR_STOLEN Nikolay Aleksandrov
2013-06-28 5:51 ` [PATCH net-next 0/3] bonding: struct bonding cleanup and MAC set fixes David Miller
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=1372259619-32430-1-git-send-email-nikolay@redhat.com \
--to=nikolay@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).