From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-sparse@vger.kernel.org
Subject: Re: linux kernel warnings/errors (#7)
Date: Tue, 23 Feb 2010 14:40:03 -0800 [thread overview]
Message-ID: <4B845943.10507@xenotime.net> (raw)
In-Reply-To: <20100223114906.61d4e001.rdunlap@xenotime.net>
On 02/23/10 11:49, Randy Dunlap wrote:
> Hi,
>
> You probably know that sparse produces a ton of errors & warnings when
> run on the Linux kernel tree (a little over 1 MB in my latest 'make C=1'
> on x86_64 arch.).
>
> I'm wondering if all of these are valid.
>
> Examples:
(one addition)
7. from drivers/gpu/drm/radeon/atombios.h:
#define VESA_OEM_PRODUCT_REV '01.00'
#define VESA_MODE_ATTRIBUTE_MODE_SUPPORT 0xBB /* refer to VBE spec p.32, no TTY support */
causes sparse to say:
drivers/gpu/drm/radeon/atombios.h:4091:63: error: Bad character constant
drivers/gpu/drm/radeon/atombios.h:4092:1: error: Bad character constant
That second one is a bit confusing. It's just a remnant of the first one...
--
~Randy
next prev parent reply other threads:[~2010-02-23 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 19:49 linux kernel warnings/errors Randy Dunlap
2010-02-23 20:59 ` Josh Triplett
2010-02-23 22:20 ` Randy Dunlap
2010-02-23 22:40 ` Randy Dunlap [this message]
2010-02-24 0:55 ` linux kernel warnings/errors (#8) Randy Dunlap
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=4B845943.10507@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-sparse@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).