From: Avi Kivity <avi@qumranet.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make LIST_POISON less deadly
Date: Tue, 20 May 2008 10:06:40 +0300 [thread overview]
Message-ID: <48327880.70104@qumranet.com> (raw)
In-Reply-To: <20080519190438.GB24599@uranus.ravnborg.org>
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
next prev parent reply other threads:[~2008-05-20 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 15:38 [PATCH] Make LIST_POISON less deadly Avi Kivity
2008-05-19 13:01 ` Ingo Molnar
2008-05-19 13:18 ` Avi Kivity
2008-05-19 13:22 ` Ingo Molnar
2008-05-19 13:35 ` Avi Kivity
2008-05-19 13:45 ` Avi Kivity
2008-05-19 19:04 ` Sam Ravnborg
2008-05-20 7:06 ` Avi Kivity [this message]
2008-05-20 11:24 ` Andi Kleen
2008-05-20 11:34 ` Avi Kivity
2008-05-20 11:49 ` Andi Kleen
2008-05-20 11:52 ` Avi Kivity
2008-05-20 12:04 ` Andi Kleen
2008-05-20 12:04 ` Ingo Molnar
2008-05-20 16:47 ` Pavel Machek
2008-05-20 16:50 ` Avi Kivity
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=48327880.70104@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.