From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Cliff Wickman <cpw@sgi•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for August 7 (SGI UV)
Date: Thu, 7 Aug 2008 15:07:50 -0700 [thread overview]
Message-ID: <20080807150750.162f816c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080807172027.8180312c.sfr@canb.auug.org.au>
(This may happen in mainline, but I haven't checked there.)
sparse complains about bitfields not being marked as signed or unsigned
and about one-bit bitfields being (default) signed (sign bit only!):
CHECK /local/linsrc/linux-next-20080807/arch/x86/kernel/tlb_64.c
include2/asm/uv/uv_bau.h:141:22: warning: dubious bitfield without explicit `signed' or `unsigned'
include2/asm/uv/uv_bau.h:143:25: warning: dubious bitfield without explicit `signed' or `unsigned'
include2/asm/uv/uv_bau.h:145:15: warning: dubious bitfield without explicit `signed' or `unsigned'
include2/asm/uv/uv_bau.h:148:14: warning: dubious bitfield without explicit `signed' or `unsigned'
include2/asm/uv/uv_bau.h:151:14: warning: dubious bitfield without explicit `signed' or `unsigned'
include2/asm/uv/uv_bau.h:154:18: warning: dubious bitfield without explicit `signed' or `unsigned'
include2/asm/uv/uv_bau.h:156:18: warning: dubious bitfield without explicit `signed' or `unsigned'
include2/asm/uv/uv_bau.h:160:14: error: dubious one-bit signed bitfield
include2/asm/uv/uv_bau.h:164:18: error: dubious one-bit signed bitfield
include2/asm/uv/uv_bau.h:178:19: error: dubious one-bit signed bitfield
include2/asm/uv/uv_bau.h:186:16: error: dubious one-bit signed bitfield
include2/asm/uv/uv_bau.h:190:18: error: dubious one-bit signed bitfield
include2/asm/uv/uv_bau.h:193:16: error: dubious one-bit signed bitfield
CC arch/x86/kernel/tlb_64.o
Can those struct bitfields be marked as signed or unsigned, please?
Thanks.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
prev parent reply other threads:[~2008-08-07 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 7:20 linux-next: Tree for August 7 Stephen Rothwell
2008-08-07 22:07 ` Randy Dunlap [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=20080807150750.162f816c.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=cpw@sgi$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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