lkml.org 
[lkml]   [2008]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Make LIST_POISON less deadly
Sam Ravnborg wrote:
>> 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.
>>
>
> Sorry - no help here. I have not tried to work that much with int in
> Kconfig.
>
>

I found some workaround (define the variable only on archs that want it,
use #ifdef to check).

> That said I really think stuff like this belongs in a header file.
> I do not agree to hide this as part of the configuration.
>

While I agree with you, I defer to Ingo on this.

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



\
 
 \ /
  Last update: 2008-05-20 09:09    [W:0.059 / U:0.596 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site