From: Veaceslav Falico <vfalico@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
j.vosburgh@gmail.com, andy@greyhouse.net, teg@jklm.no,
jay.vosburgh@canonical.com, mkubecek@suse.cz
Subject: Re: [patch net-next] bonding: remove no longer relevant vlan warnings
Date: Wed, 2 Jul 2014 14:03:08 +0200 [thread overview]
Message-ID: <20140702120308.GA2596@mikrodark.usersys.redhat.com> (raw)
In-Reply-To: <1404294938-9968-1-git-send-email-jiri@resnulli.us>
On Wed, Jul 02, 2014 at 11:55:38AM +0200, Jiri Pirko wrote:
>These warnings are no longer relevant. Even when last slave is
>removed, there is a valid address assigned to bond (random).
>The correct functionality of vlans is ensured by maintaining unicast
>list in vlan_sync_address().
>
>Suggested-by: Jay Vosburgh <jay.vosburgh@canonical.com>
>Signed-off-by: Jiri Pirko <jiri@resnulli.us>
Thanks for following up on this.
Acked-by: Veaceslav Falico <vfalico@gmail.com>
>---
> drivers/net/bonding/bond_main.c | 7 -------
> 1 file changed, 7 deletions(-)
>
>diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
>index ffefb70..09dc3ef 100644
>--- a/drivers/net/bonding/bond_main.c
>+++ b/drivers/net/bonding/bond_main.c
>@@ -1754,13 +1754,6 @@ static int __bond_release_one(struct net_device *bond_dev,
> if (!bond_has_slaves(bond)) {
> bond_set_carrier(bond);
> eth_hw_addr_random(bond_dev);
>-
>- if (vlan_uses_dev(bond_dev)) {
>- pr_warn("%s: Warning: clearing HW address of %s while it still has VLANs\n",
>- bond_dev->name, bond_dev->name);
>- pr_warn("%s: When re-adding slaves, make sure the bond's HW address matches its VLANs\n",
>- bond_dev->name);
>- }
> }
>
> unblock_netpoll_tx();
>--
>1.9.0
>
next prev parent reply other threads:[~2014-07-02 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:55 [patch net-next] bonding: remove no longer relevant vlan warnings Jiri Pirko
2014-07-02 12:03 ` Veaceslav Falico [this message]
2014-07-08 4:32 ` 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=20140702120308.GA2596@mikrodark.usersys.redhat.com \
--to=vfalico@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=j.vosburgh@gmail.com \
--cc=jay.vosburgh@canonical.com \
--cc=jiri@resnulli.us \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=teg@jklm.no \
/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).