public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: fake config option w/kbuild?
Date: Thu, 15 Mar 2007 20:12:59 +0100	[thread overview]
Message-ID: <20070315191258.GA752@stusta.de> (raw)
In-Reply-To: <C6F49569-655E-4B17-B9DA-9644C8B3668D@kernel.crashing.org>

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


> thanks
> 
> - kumar

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-03-15 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 15:19 fake config option w/kbuild? Kumar Gala
2007-03-15 19:12 ` Adrian Bunk [this message]
2007-03-15 20:08   ` Kumar Gala
2007-03-17 23:33     ` Adrian Bunk
2007-03-18 16:24 ` Roman Zippel

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=20070315191258.GA752@stusta.de \
    --to=bunk@stusta.de \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox