From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>
Cc: davem@davemloft.net, Jiri Pirko <jiri@resnulli.us>,
Wang Chen <wangchen@cn.fujitsu.com>,
Veaceslav Falico <vfalico@redhat.com>,
Nikolay Aleksandrov <nikolay@redhat.com>
Subject: [PATCH net 0/3] bonding: a bunch of fixes for dev hwaddr sync in bond_enslave
Date: Mon, 26 Mar 2018 01:16:44 +0800 [thread overview]
Message-ID: <cover.1521997984.git.lucien.xin@gmail.com> (raw)
This patchset is mainly to fix a crash when adding vlan as slave of
bond which is also the parent link in patch 2/3, and also fix some
err process problems in bond_enslave in patch 1/3 and 3/3.
Xin Long (3):
bonding: fix the err path for dev hwaddr sync in bond_enslave
bonding: move dev_mc_sync after master_upper_dev_link in bond_enslave
bonding: process the err returned by dev_set_allmulti properly in
bond_enslave
drivers/net/bonding/bond_main.c | 73 +++++++++++++++++++++--------------------
1 file changed, 37 insertions(+), 36 deletions(-)
--
2.1.0
next reply other threads:[~2018-03-25 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 17:16 Xin Long [this message]
2018-03-25 17:16 ` [PATCH net 1/3] bonding: fix the err path for dev hwaddr sync in bond_enslave Xin Long
2018-03-25 17:16 ` [PATCH net 2/3] bonding: move dev_mc_sync after master_upper_dev_link " Xin Long
2018-03-25 17:16 ` [PATCH net 3/3] bonding: process the err returned by dev_set_allmulti properly " Xin Long
2018-03-26 16:07 ` Andy Gospodarek
2018-03-26 15:46 ` [PATCH net 2/3] bonding: move dev_mc_sync after master_upper_dev_link " Andy Gospodarek
2018-03-26 14:06 ` [PATCH net 1/3] bonding: fix the err path for dev hwaddr sync " Nikolay Aleksandrov
2018-03-26 15:16 ` Andy Gospodarek
2018-03-26 14:16 ` [PATCH net 0/3] bonding: a bunch of fixes " Nikolay Aleksandrov
2018-03-26 16:52 ` 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=cover.1521997984.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--cc=vfalico@redhat.com \
--cc=wangchen@cn.fujitsu.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).