public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	lkml <linux-kernel@vger.kernel.org>,
	zippel@linux-m68k.org, jejb <james.bottomley@steeleye.com>
Subject: Re: how to handle indirect kconfig dependencies
Date: Mon, 20 Nov 2006 19:13:19 +0100	[thread overview]
Message-ID: <20061120181319.GX31879@stusta.de> (raw)
In-Reply-To: <455DBF3D.40801@s5r6.in-berlin.de>

On Fri, Nov 17, 2006 at 02:55:09PM +0100, Stefan Richter wrote:
> Randy Dunlap wrote:
> > I have a (randconfig) build of 2.6.19-rc5-mm2 with:
> [...]
> > so the question is:
> > (How) can kconfig follow the dependency chain and either
> > - prevent this odd config combination or
> > - see that 'select DEBUG_FS' implies 'select SYSFS' and then enable SYSFS
> > ?
> > 
> > I don't believe that the right answer is to add
> > 	depends on SYSFS
> > to DEBUG_READAHEAD.
> 
> I know this doesn't concludingly answer your question, but: All of the
> various shipped tools to generate .config need to be fixed to recognize
> "select" to imply a dependency like "depends on" does.
>...

BTW:
"All of the various shipped tools ... need to be fixed" is a bit 
misleading since one of the features of the 2.6 kconfig is that this 
code is shared by all tools.

> Stefan Richter

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:[~2006-11-20 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17  4:07 how to handle indirect kconfig dependencies Randy Dunlap
2006-11-17 13:55 ` Stefan Richter
2006-11-20 18:13   ` Adrian Bunk [this message]
2006-11-20 18:56     ` Stefan Richter
2006-11-20 22:09 ` James Bottomley
2006-11-26  3:46 ` Randy Dunlap

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=20061120181319.GX31879@stusta.de \
    --to=bunk@stusta.de \
    --cc=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --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