All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Greg KH <gregkh@suse.de>, lkml <linux-kernel@vger.kernel.org>,
	Lucian Adrian Grijincu <lgrijincu@ixiacom.com>
Subject: Re: [PATCH] documentation: make it clear that sysfs is optional
Date: Sat, 1 Aug 2009 09:49:24 -0700	[thread overview]
Message-ID: <20090801094924.ba245b4c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0908010157150.5831@bogon.housecafe.de>

On Sat, 1 Aug 2009 02:14:47 -0700 (PDT) Christian Kujau wrote:

> On Mon, 27 Jul 2009 at 09:26, Greg KH wrote:
> > Probably the same reason /proc is configurable.  No one ever turns it
> > off, but hey, it's possible :)
> 
> Hm, it seems as we cannot turn off PROC_FS or SYSFS any more. At least on 
> my system a "make allnoconfig" still selects both. While PROC_FS still 
> shows up under Filesystems->Pseudo-Filesystem (but cannot be turned off), 
> I don't see a menuconfig knob to turn off SYSFS.
> However, "make allnoconfig" still selects quite a few options anyway:
> 
> # uname -m
> x86_64
> # make allnoconfig
> # grep -c =y .config
> 175
> 
> (manually editing .config gets reverted on another "make config").
> 
> So, it loks like SYSFS is just one of the things needed to build a kernel, 
> along with the ~170 other things, at least on x86_64. Is this "make it 
> clear that sysfs is optional" patch still valid? :-)


It's no problem to disable PROC_FS and SYSFS if you first enable
CONFIG_EMBEDDED>


> sid$ find . -name Kconfig | xargs grep SYSFS  | egrep -v 'drivers/|fs/|net/'
> ./arch/arm/mach-pxa/Kconfig:    select GPIO_SYSFS
> ./arch/powerpc/kvm/Kconfig:     depends on KVM && MARKERS && SYSFS
> ./arch/x86/kvm/Kconfig: depends on KVM && SYSFS
> ./init/Kconfig:config SYSFS_DEPRECATED
> ./init/Kconfig:config SYSFS_DEPRECATED_V2
> ./init/Kconfig: depends on SYSFS
> ./init/Kconfig: select SYSFS_DEPRECATED
> ./init/Kconfig: depends on SLUB && SYSFS
> ./kernel/trace/Kconfig: depends on SYSFS
> ./security/Kconfig:     depends on SYSFS


---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

      reply	other threads:[~2009-08-01 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 16:06 [PATCH] documentation: make it clear that sysfs is optional Randy Dunlap
2009-07-27 16:10 ` Greg KH
2009-07-27 16:18   ` Randy Dunlap
2009-07-27 16:26     ` Greg KH
2009-07-27 22:49       ` Henrique de Moraes Holschuh
2009-07-27 23:21         ` Greg KH
2009-08-01  9:14       ` Christian Kujau
2009-08-01 16:49         ` 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=20090801094924.ba245b4c.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=gregkh@suse.de \
    --cc=lgrijincu@ixiacom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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.