From: David Miller <davem@davemloft.net>
To: fubar@us.ibm.com
Cc: jpirko@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] bonding: fix return value of couple of store functions
Date: Tue, 25 Jan 2011 13:13:42 -0800 (PST) [thread overview]
Message-ID: <20110125.131342.183052964.davem@davemloft.net> (raw)
In-Reply-To: <304.1295989626@death>
From: Jay Vosburgh <fubar@us.ibm.com>
Date: Tue, 25 Jan 2011 13:07:06 -0800
> Jiri Pirko <jpirko@redhat.com> wrote:
>
>>count is incorrectly returned even in case of fail. Return ret instead.
>>
>>Signed-off-by: Jiri Pirko <jpirko@redhat.com>
>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
Applied, thanks guys.
prev parent reply other threads:[~2011-01-25 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 18:53 [PATCH net-next-2.6] bonding: fix return value of bonding_store_slaves_active() Jiri Pirko
2011-01-25 19:22 ` Jay Vosburgh
2011-01-25 20:52 ` Jiri Pirko
2011-01-25 21:03 ` [PATCH net-next-2.6] bonding: fix return value of couple of store functions Jiri Pirko
2011-01-25 21:07 ` Jay Vosburgh
2011-01-25 21:13 ` David Miller [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=20110125.131342.183052964.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jpirko@redhat.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).