From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, gregkh@suse•de
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for July 12 (debugfs/sysfs/rcu)
Date: Mon, 12 Jul 2010 12:47:50 -0700 [thread overview]
Message-ID: <20100712124750.8ab5e870.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100712155109.d997bf1c.sfr@canb.auug.org.au>
On Mon, 12 Jul 2010 15:51:09 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100709:
Greg,
What is there about debugfs that requires sysfs?
(lib/Kconfig.debug:)
config DEBUG_FS
bool "Debug Filesystem"
depends on SYSFS
I ask because kconfig now (in linux-next) warns about kconfig dependency
problems, like this one:
warning: (TREE_RCU_TRACE || AMD_IOMMU_STATS && AMD_IOMMU || MTD_UBI_DEBUG && MTD && SYSFS && MTD_UBI || UBIFS_FS_DEBUG && MISC_FILESYSTEMS && UBIFS_FS || DEBUG_KMEMLEAK && DEBUG_KERNEL && EXPERIMENTAL && !MEMORY_HOTPLUG && (X86 || ARM || PPC || S390 || SPARC64 || SUPERH || MICROBLAZE) && SYSFS || TRACING || X86_PTDUMP && DEBUG_KERNEL || BLK_DEV_IO_TRACE && TRACING_SUPPORT && FTRACE && SYSFS && BLOCK) selects DEBUG_FS which has unmet direct dependencies (SYSFS)
because TREE_RCU_TRACE selects DEBUG_FS, even when SYSFS is not enabled.
I first made a patch to have TREE_RCU_TRACE depend on SYSFS, but then I just
removed the DEBUG_FS "depends on SYSFS" and the kernel builds fine,
hence the first question.
thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-07-12 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 5:51 linux-next: Tree for July 12 Stephen Rothwell
2010-07-12 19:47 ` Randy Dunlap [this message]
2010-07-12 21:21 ` linux-next: Tree for July 12 (debugfs/sysfs/rcu) Greg KH
2010-07-20 23:04 ` [PATCH -next] debugfs: no longer needs to depend on SYSFS 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=20100712124750.8ab5e870.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=gregkh@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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