From: Greg KH <greg@kroah.com>
To: Davidlohr Bueso <dave@gnu.org>
Cc: mochel@osdl.org, mamurph@cs.clemson.edu,
LKML <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: Outdated sysfs.txt document?
Date: Wed, 11 Aug 2010 17:23:56 -0700 [thread overview]
Message-ID: <20100812002356.GA12214@kroah.com> (raw)
In-Reply-To: <1281564321.1934.5.camel@cowboy>
On Wed, Aug 11, 2010 at 06:05:21PM -0400, Davidlohr Bueso wrote:
> Hi,
Any reason you didn't send this to the current sysfs maintainer?
> I have been going through Documentation/filesystems/sysfs.txt, and
> noticed what I believe to be either outdated or incomplete:
>
> The "Top Level Directory Layout" mentions
> block/
> bus/
> class/
> dev/
> devices/
> firmware/
> net/
> fs/
>
> We seem to be missing kernel, power, hypervisor, module, etc.
>
> dave@cowboy:~$ ls /sys/
> block class devices fs kernel power
> bus dev firmware hypervisor module
>
> I am preparing a patch to complete this, but could someone confirm first
> that this is actually what is meant.
It would be nice to have it match up to reality, Documentation usually
lags.
thanks,
greg k-h
prev parent reply other threads:[~2010-08-12 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 22:05 Outdated sysfs.txt document? Davidlohr Bueso
2010-08-12 0:23 ` Greg KH [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=20100812002356.GA12214@kroah.com \
--to=greg@kroah.com \
--cc=dave@gnu.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mamurph@cs.clemson.edu \
--cc=mochel@osdl.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