All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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 14:21:26 -0700	[thread overview]
Message-ID: <20100712212126.GA2684@suse.de> (raw)
In-Reply-To: <20100712124750.8ab5e870.randy.dunlap@oracle.com>

On Mon, Jul 12, 2010 at 12:47:50PM -0700, Randy Dunlap wrote:
> 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?

Look at commit 3348e05a4f25489908d9f7ed4e80ac291ead18f4 almost 5 years
ago:
    [PATCH] DEBUG_FS must depend on SYSFS
    
    CONFIG_DEBUG_FS=y and CONFIG_SYSFS=n results in the following compile
    error:
    
    <--  snip  -->
    
    ...
      LD      vmlinux
    fs/built-in.o: In function `debugfs_init':
    inode.c:(.init.text+0x31be): undefined reference to `kernel_subsys'
    make: *** [vmlinux] Error 1
    
    <--  snip  -->

But, there is no "kernel_subsys" anymore, it is called kernel_kobj, and
is in kernel/ksysfs.c and always is built now, even if CONFIG_SYSFS is
disabled.

So it should be safe to remove that dependancy if you want to.

thanks,

greg k-h

  reply	other threads:[~2010-07-12 21:22 UTC|newest]

Thread overview: 5+ 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 ` linux-next: Tree for July 12 (debugfs/sysfs/rcu) Randy Dunlap
2010-07-12 21:21   ` Greg KH [this message]
2010-07-20 23:04     ` [PATCH -next] debugfs: no longer needs to depend on SYSFS Randy Dunlap
2010-07-21 20:15       ` patch "debugfs: no longer needs to depend on SYSFS" added to gregkh-2.6 tree gregkh

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=20100712212126.GA2684@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.