From: Hans de Goede <hdegoede@redhat.com>
To: Emil Goode <emilgoode@gmail.com>
Cc: mchehab@infradead.org, linux-media@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] [media] gspca: dubious one-bit signed bitfield
Date: Mon, 06 Aug 2012 10:21:35 +0200 [thread overview]
Message-ID: <501F7E8F.1090809@redhat.com> (raw)
In-Reply-To: <1344170066-19727-1-git-send-email-emilgoode@gmail.com>
Hi,
On 08/05/2012 02:34 PM, Emil Goode wrote:
> This patch changes some signed integers to unsigned because
> they are not intended for negative values and sparse
> is making noise about it.
>
> Sparse gives eight of these errors:
> drivers/media/video/gspca/ov519.c:144:29: error: dubious one-bit signed bitfield
>
> Signed-off-by: Emil Goode <emilgoode@gmail.com>
Thanks, I'll add this to my gspca tree.
Regards,
Hans
next prev parent reply other threads:[~2012-08-06 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 12:34 [PATCH] [media] gspca: dubious one-bit signed bitfield Emil Goode
2012-08-06 8:21 ` Hans de Goede [this message]
2012-08-09 11:28 ` Hans de Goede
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=501F7E8F.1090809@redhat.com \
--to=hdegoede@redhat.com \
--cc=emilgoode@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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).