mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: gregkh@suse.de, Lucian Adrian Grijincu <lgrijincu@ixiacom.com>
Subject: [PATCH] documentation: make it clear that sysfs is optional
Date: Mon, 27 Jul 2009 09:06:42 -0700	[thread overview]
Message-ID: <20090727090642.0e495919.randy.dunlap@oracle.com> (raw)

From:	Lucian Adrian Grijincu <lgrijincu@ixiacom.com>
Subject: [PATCH] documentation: make it clear that sysfs is optional

The original text suggested that sysfs is mandatory and always
compiled in the kernel.

Signed-off-by: Lucian Adrian Grijincu <lgrijincu@ixiacom.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 Documentation/filesystems/sysfs.txt |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

--- linux-next-20090727.orig/Documentation/filesystems/sysfs.txt
+++ linux-next-20090727/Documentation/filesystems/sysfs.txt
@@ -23,7 +23,8 @@ interface. 
 Using sysfs
 ~~~~~~~~~~~
 
-sysfs is always compiled in. You can access it by doing:
+sysfs is always compiled in if CONFIG_SYSFS is defined. You can access
+it by doing:
 
     mount -t sysfs sysfs /sys 
 


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

             reply	other threads:[~2009-07-27 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 16:06 Randy Dunlap [this message]
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

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=20090727090642.0e495919.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=gregkh@suse.de \
    --cc=lgrijincu@ixiacom.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome