From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm <akpm@osdl.org>, ak@suse.de
Subject: [PATCH] x86_64: use UL on TASK_SIZE
Date: Sat, 22 Jan 2005 22:56:17 -0800 [thread overview]
Message-ID: <20050122225617.35d1c6ac.rddunlap@osdl.org> (raw)
Use UL on large constant (kills 3214 sparse warnings :)
include/linux/sched.h:1150:18: warning: constant 0x800000000000 is so big it is long
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
include/asm-x86_64/processor.h | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Naurp ./include/asm-x86_64/processor.h~proc_task_size ./include/asm-x86_64/processor.h
--- ./include/asm-x86_64/processor.h~proc_task_size 2005-01-22 19:06:33.765150024 -0800
+++ ./include/asm-x86_64/processor.h 2005-01-22 21:40:48.884158072 -0800
@@ -162,7 +162,7 @@ static inline void clear_in_cr4 (unsigne
/*
* User space process size. 47bits.
*/
-#define TASK_SIZE (0x800000000000)
+#define TASK_SIZE (0x800000000000UL)
/* This decides where the kernel will search for a free chunk of vm
* space during mmap's.
--
next reply other threads:[~2005-01-23 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 6:56 Randy.Dunlap [this message]
2005-01-23 10:59 ` Andi Kleen
2005-01-23 18:16 ` 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=20050122225617.35d1c6ac.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®