linux-kernel - Re: fake config option w/kbuild?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Mar 2007 15:08:47 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Roman Zippel <zippel@...ux-m68k.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: fake config option w/kbuild?


On Mar 15, 2007, at 2:12 PM, Adrian Bunk wrote:

> On Thu, Mar 15, 2007 at 10:19:03AM -0500, Kumar Gala wrote:
>> ...
>> My initial question is that I don't want anyone using CONFIG_QE_83xx
>> or CONFIG_QE_85xx in code, the second part is if there is a way to
>> remove duplicating the QE_83xx/QE_85xx options down in platform/8 
>> {3,5}
>> xx/Kconfig.
>
>
> What about the following solution:
>
>
> arch/powerpc/Kconfig.qe:
>
> <--  snip  -->
>
> config MACH_SUPPORTS_QE
> 	bool
>
> config QE
> 	bool "QUICC Engine Support"
> 	depends on MACH_SUPPORTS_QE
> 	help
> 	  ...
>
> <--  snip  -->
>
>
> arch/powerpc/platforms/83xx/Kconfig:
>
> <--  snip  -->
>
> ...
> source arch/powerpc/Kconfig.qe
>
> config PPC_MPC836x
>         bool
> 	select MACH_SUPPORTS_QE
> 	...
> ....
>
> <--  snip  -->

Not sure this helps since I end up having to source arch/powerpc/ 
Kconfig.qe from both arch/powerpc/platforms/83xx/Kconfig & arch/ 
powerpc/platforms/85xx/Kconfig and then mconf grips about having  
already scanned Kconfig.qe.

- k

-
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/