From: "Peter Teoh" <htmldeveloper@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Scott Lovenberg" <scott.lovenberg@gmail.com>,
"Randy Dunlap" <randy.dunlap@oracle.com>,
"Mulyadi Santosa" <mulyadi.santosa@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
"Rik van Riel" <riel@redhat.com>
Subject: Re: Documentation about sysfs/procfs entries
Date: Wed, 13 Feb 2008 15:40:32 +0800 [thread overview]
Message-ID: <804dabb00802122340t555e3c26ma903ef97991dd13@mail.gmail.com> (raw)
In-Reply-To: <20080213073159.GA13414@kroah.com>
On 2/13/08, Greg KH <greg@kroah.com> wrote:
> On Wed, Feb 13, 2008 at 12:59:43AM -0500, Scott Lovenberg wrote:
> > Randy Dunlap wrote:
> >> On Wed, 13 Feb 2008 09:08:12 +0700 Mulyadi Santosa wrote:
> >>
> >>
> >>> Hi all...
> >>>
> >>> Here's my idea: what if we collaborate to extend and make the kernel
> >>> documentation better? I have done (slow) start by editing profile=
> >>> kernel param. It's not accepted by Adrian Bunk, but at least I did it.
> >>> Feedback?
> >>>
> >>
> >> Adrian is no longer the trivial patch maintainer.
> >> Did you send the patch to trivial@kernel.org ?
> >>
> >> Any doc additions or improvements would be appreciated.
> >> I'll be glad to help get them merged...
> >>
> >> ---
> >> ~Randy
> >>
> >>
> > I'd love to help, but I'm a bit of a newbie; what's protocol for
> > documentation updates, standard diffs?
>
> Yes.
>
> > How are we going to attack this thing, cleaning up and updating existing
> > documentation first and then adding undocumented items, or file by file
> > updating and adding in one fell swoop?
>
> File by file.
>
> And please place the new documentation of sysfs and procfs entries into
> the framework in the Documentation/ABI/ directory tree, which is where
> it belongs.
>
> thanks,
>
> greg k-h
>
some questions:
a. the list of parameters can presumably be extracted from existing
file via "procname" search.....not sure if it is correct (as per
attached, complete?)
b. what is the diff between /proc and /sys? in
Documentation/filesystems/proc.txt....it is mentioned that /proc
information will be published into a book...where is it? I can never
understand this.
c. in Doc/sysctl are all the explanation for /proc/sys/* .... as a
start i think we shall contribute fixing here....but according to your
email, we should fix Doc/ABI...so I supposed some migration is needed?
d. In networking/ip-sysctl.txt a lot of the explanation for the
attached procname's parameters are explained, may be we can relocate
it to ABI?
next prev parent reply other threads:[~2008-02-13 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <804dabb00802112123t774623b2n3e1e0a4addde1512@mail.gmail.com>
[not found] ` <b1fc6a560802112217j57ab3fa1h611864a6a2423943@mail.gmail.com>
2008-02-12 6:24 ` Scott Lovenberg
2008-02-12 7:46 ` Peter Teoh
[not found] ` <47B15DD2.3090706@gmail.com>
2008-02-13 2:08 ` Mulyadi Santosa
2008-02-13 4:43 ` Randy Dunlap
2008-02-13 5:48 ` Peter Teoh
[not found] ` <47B2874F.5000805@gmail.com>
2008-02-13 6:03 ` Manish Katiyar
2008-02-13 7:31 ` Greg KH
2008-02-13 7:40 ` Peter Teoh [this message]
2008-02-13 8:25 ` Greg KH
2008-02-13 9:00 ` Peter Teoh
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=804dabb00802122340t555e3c26ma903ef97991dd13@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=greg@kroah.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mulyadi.santosa@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=riel@redhat.com \
--cc=scott.lovenberg@gmail.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
all inboxes | Powered by JetHome®