From: Pavel Roskin <proski@gnu.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] wireless: at76c50x: signedness bug in at76_dfu_get_state()
Date: Thu, 9 Aug 2012 17:18:19 -0400 [thread overview]
Message-ID: <20120809171819.00c66bee@mj> (raw)
In-Reply-To: <20120809065730.GA7925@elgon.mountain>
On Thu, 9 Aug 2012 09:57:30 +0300
Dan Carpenter <dan.carpenter@oracle.com> wrote:
> This return holds the number of bytes transfered (1 byte) or a
> negative error code. The type should be int instead of u8.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Acked-by: Pavel Roskin <proski@gnu.org>
Nice catch, thanks!
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2012-08-09 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 6:57 [patch] wireless: at76c50x: signedness bug in at76_dfu_get_state() Dan Carpenter
2012-08-09 21:18 ` Pavel Roskin [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=20120809171819.00c66bee@mj \
--to=proski@gnu.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).