[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ECA2FF6.2090708@gaisler.com>
Date: Mon, 21 Nov 2011 12:03:18 +0100
From: Konrad Eisele <konrad@...sler.com>
To: Michal Marek <mmarek@...e.cz>
CC: Arnaud Lacombe <lacombar@...il.com>,
Randy Dunlap <rdunlap@...otime.net>,
linux-kernel@...r.kernel.org,
linux kbuild list <linux-kbuild@...r.kernel.org>,
pefoley2@...izon.net, yann.morin.1998@...iens.enib.fr,
sam@...nborg.org, zippel@...ux-m68k.org
Subject: Re: [PATCH 1/1] kconfig: Add a configuration subtree command to kconfig
Michal Marek wrote:
> On 19.11.2011 08:52, konrad.gaisler wrote:
>> On 11/19/2011 07:23 AM, Arnaud Lacombe wrote:
>>> On Fri, Nov 18, 2011 at 5:51 PM, konrad.gaisler<konrad@...sler.com> wrote:
>>>> As an example, apply the patch, then add to<top>/Kconfig the lines:
>>>>
>>>> subsource "arch/sparc/Kconfig" "." ".config_sparc" "SPARC config" SPARC_
>>>> CONFIG_
>>>> subsource "arch/mips/Kconfig" "." ".config_mips" "MIPS config" MIPS_ CONFIG_
>>>>
>>> ETOOMUCHARGUMENT!
>>>
>>> I wonder if we could not get all these parameters specified
>>> dynamically in the Kconfig. This would replace the `mainmenu' entry
>>> ala:
>>>
>>> config
>>> title "Linux ..."
>>> prefix "CONFIG_"
>>> file .config
>>> endconfig
>> Yes maybe it can be done that way. Personally I think it is
>> more difficult.
>
> A <command> <argument> syntax fits well into the existing Kconfig
> language and it more readable, as you don't have to count the position
> of the arguments and check their meaning in the documentation.
>
> Michal
>
>
Ok, I'll do it with "Config" and type "title". It will
take a while until I have a new patch...
-- Konrad
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists