lkml.org 
[lkml]   [2008]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Make LIST_POISON less deadly
Ingo Molnar wrote:
> i'd suggest to add an ARCH_ILLEGAL_POINTER define instead, which
> defaults to zero and gets added to pointer-ish poison values. That makes
> it both simpler and also it does not need any include/asm changes
> because ARCH_ILLEGAL_POINTER can be set from the Kconfig space.
>

Any idea how to override a value in Kconfig? We can do it for bool
values but not strings.

e.g.

lib/Kconfig:
config ILLEGAL_POINTER_VALUE
hex
default 0

arch/x86/Kconfig:
config X86
select ILLEGAL_POINTER_VALUE=0x80000000000000000000000000 if X86_64

?

I could do it with a boolean signifying existence and a hex for the
value, but I'd rather not.

--
error compiling committee.c: too many arguments to function



\
 
 \ /
  Last update: 2008-05-19 15:47    [W:0.100 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site