public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: zippel@linux-m68k.org, jejb <james.bottomley@steeleye.com>
Subject: Re: how to handle indirect kconfig dependencies
Date: Sat, 25 Nov 2006 19:46:54 -0800	[thread overview]
Message-ID: <20061125194654.2391db44.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20061116200741.fb607fe4.randy.dunlap@oracle.com>

On Thu, 16 Nov 2006 20:07:41 -0800 Randy Dunlap wrote:

> Hi,
> 
> I have a (randconfig) build of 2.6.19-rc5-mm2 with:
> 
> CONFIG_DEBUG_READAHEAD=y
> 
> which selects DEBUG_FS, so DEBUG_FS=y, but DEBUG_FS depends on
> SYSFS, and SYSFS is not set in the randconfig.
> 
> This randconfig causes this build error:
> 
> fs/built-in.o: In function `debugfs_init':
> inode.c:(.init.text+0xdb2): undefined reference to `kernel_subsys'
> 
> 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.
> 
> 
> .config is at http://oss.oracle.com/~rdunlap/configs/config-readahead-debugfs

Roman,
Here's another one for your consideration.

USB_APPLEDISPLAY selects BACKLIGHT_LCD_SUPPORT & BACKLIGHT_CLASS_DEVICE;
drivers/backlight/Kconfig depends on SYSFS (but SYSFS=n)

http://oss.oracle.com/~rdunlap/configs/config-backlight-appledisplay

---
~Randy

      parent reply	other threads:[~2006-11-26  3:46 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
2006-11-20 18:56     ` Stefan Richter
2006-11-20 22:09 ` James Bottomley
2006-11-26  3:46 ` Randy Dunlap [this message]

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=20061125194654.2391db44.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.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