From: Veaceslav Falico <vfalico@redhat.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>, Netdev <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v2.1 0/3] bonding: fix primary problem for bonding
Date: Tue, 14 Jan 2014 11:55:37 +0100 [thread overview]
Message-ID: <20140114105537.GD20066@redhat.com> (raw)
In-Reply-To: <52D5174D.4070807@huawei.com>
On Tue, Jan 14, 2014 at 06:54:05PM +0800, Ding Tianhong wrote:
>If the slave's name changed, and the bond params primary is exist,
>the bond should deal with the situation in two ways:
>
>1) If the slave was the primary slave yet, clean the primary slave
> and reselect active slave.
>2) If the slave's new name is as same as bond primary, set the slave
> as primary slave and reselect active slave.
>
>If the new primary is not matching any slave in the bond, the bond should
>record it to params, clean the primary slave and select a new active slave.
>
>Update bonding.txt for primary description.
>
>v2.1 Because there are too many indentions and useless verification, so rewrite
> the logic for updating the primary slave.
> Modify some comments for to clean the typos.
LOL. That's exactly what I was talking about in my previous email. A quick
fix that doesn't even address the issues.
Nacked-by: Veaceslav Falico <vfalico@redhat.com>
>
>Ding Tianhong (3):
> bonding: update the primary slave when changing slave's name
> bonding: clean the primary slave if there is no slave matching new
> primary
> bonding: update bonding.txt for primary description.
>
> Documentation/networking/bonding.txt | 3 ++-
> drivers/net/bonding/bond_main.c | 24 ++++++++++++++++++++++--
> drivers/net/bonding/bond_options.c | 6 ++++++
> 3 files changed, 30 insertions(+), 3 deletions(-)
>
>--
>1.8.0
>
>
>
prev parent reply other threads:[~2014-01-14 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 10:54 [PATCH net-next v2.1 0/3] bonding: fix primary problem for bonding Ding Tianhong
2014-01-14 10:55 ` Veaceslav Falico [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=20140114105537.GD20066@redhat.com \
--to=vfalico@redhat.com \
--cc=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.