From: Veaceslav Falico <vfalico@redhat.com>
To: nikolay@redhat.com
Cc: netdev@vger.kernel.org, andy@greyhouse.net, fubar@us.ibm.com,
davem@davemloft.net
Subject: Re: bonding: fix slave speed reporting in bond_miimon_commit
Date: Thu, 20 Jun 2013 15:42:48 +0200 [thread overview]
Message-ID: <20130620134247.GA1157@redhat.com> (raw)
In-Reply-To: <1371731653-13568-1-git-send-email-nikolay@redhat.com>
On Thu, Jun 20, 2013 at 02:34:13PM +0200, nikolay@redhat.com wrote:
>From: Nikolay Aleksandrov <nikolay@redhat.com>
>
>When we have BOND_LINK_UP the speed is reported unconditionally with %u
>format although it can be SPEED_UNKNOWN (-1). After this patch it returns
>0 in that case in an attempt to keep the existing scripts happy.
>One line is intenionally left 81 chars because it gets ugly if broken.
>
>Signed-off-by: Nikolay Aleksandrov <nikolay@redhat.com>
>
Acked-by: Veaceslav Falico <vfalico@redhat.com>
next prev parent reply other threads:[~2013-06-20 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 12:34 [PATCH] bonding: fix slave speed reporting in bond_miimon_commit nikolay
2013-06-20 13:42 ` Veaceslav Falico [this message]
2013-06-24 7:05 ` 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=20130620134247.GA1157@redhat.com \
--to=vfalico@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.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).