From: Greg KH <gregkh@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
Lucian Adrian Grijincu <lgrijincu@ixiacom.com>
Subject: Re: [PATCH] documentation: make it clear that sysfs is optional
Date: Mon, 27 Jul 2009 16:21:45 -0700 [thread overview]
Message-ID: <20090727232144.GA29954@suse.de> (raw)
In-Reply-To: <20090727224930.GB6932@khazad-dum.debian.net>
On Mon, Jul 27, 2009 at 07:49:30PM -0300, Henrique de Moraes Holschuh wrote:
> On Mon, 27 Jul 2009, Greg KH wrote:
> > On Mon, Jul 27, 2009 at 09:18:24AM -0700, Randy Dunlap wrote:
> > > On Mon, 27 Jul 2009 09:10:33 -0700 Greg KH wrote:
> > > > On Mon, Jul 27, 2009 at 09:06:42AM -0700, Randy Dunlap wrote:
> > > > > The original text suggested that sysfs is mandatory and always
> > > > > compiled in the kernel.
> > > >
> > > > But it should be :)
> > >
> > > Well, you have the option of making it non-optional.
> > >
> > > > Seriously, who turns sysfs off these days, does anyone? If so, why?
> > >
> > > Why is it configurable then?
> >
> > Probably the same reason /proc is configurable. No one ever turns it
> > off, but hey, it's possible :)
>
> But does anyone ever test if the system doesn't go to lunch when you do
> that?
I have no idea, I doubt it...
next prev parent reply other threads:[~2009-07-27 23:24 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 [this message]
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=20090727232144.GA29954@suse.de \
--to=gregkh@suse.de \
--cc=hmh@hmh.eng.br \
--cc=lgrijincu@ixiacom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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