public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Greg KH <gregkh@suse.de>
Cc: mtk-lkml@gmx.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] HOWTO do Linux kernel development
Date: Thu, 17 Nov 2005 13:12:31 +0100 (MET)	[thread overview]
Message-ID: <3210.1132229551@www25.gmx.net> (raw)
In-Reply-To: 20051117065636.GC20684@suse.de

Greg,

> > Under 'Documentation', there is the text:
> > 
> >     When new features are added to the kernel, it is recommended 
> >     that new documentation files are also added which explain how 
> >     to use the feature.
> > 
> > Could you also add something like:
> > 
> >     When a new feature changes the interface that the kernel 
> >     exposes to userland, it is recommended that you send 
> >     information or a man-pages patch explaining the change 
> >     to the manual pages maintainer at mtk-manpages@gmx.net.
> 
> Do you want to start documenting the sysfs tree interface?  

There should be a sysfs(5) man page.  Unfortunately there is 
not one yet.  If someone wants to start one off...

> Do you have
> man pages for all of the kernel syscalls now?

All, no.  Most, yes.

> Anyway, I'll add it, as it is better to error on the side of caution
> here.

Thanks.

Michael

-- 
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 

Want to help with man page maintenance?  Grab the latest
tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/
and grep the source files for 'FIXME'.

  reply	other threads:[~2005-11-17 12:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 22:07 [RFC] HOWTO do Linux kernel development Greg KH
2005-11-14 22:10 ` Greg KH
2005-11-14 22:43   ` [RFC] [HUMOR] " Jeffrey V. Merkey
2005-11-15  0:18   ` [RFC] " Kalin KOZHUHAROV
2005-11-15  0:32     ` Randy.Dunlap
2005-11-15  4:58     ` Greg KH
2005-11-15  8:37       ` Paolo Ciarrocchi
2005-11-15 19:04         ` Greg KH
2005-11-15  0:32   ` Josh Boyer
2005-11-15  1:25     ` Paul Jackson
2005-11-15  1:31       ` Randy.Dunlap
2005-11-15  2:16       ` Josh Boyer
2005-11-15  2:42         ` Paul Jackson
2005-11-15  2:52           ` Josh Boyer
2005-11-15  3:01             ` Paul Jackson
2005-11-15  4:48               ` Greg KH
2005-11-15  4:47             ` Greg KH
2005-11-15  1:08 ` Coywolf Qi Hunt
2005-11-15  4:38   ` Greg KH
2005-11-15  5:51     ` Coywolf Qi Hunt
2005-11-15  5:52       ` Greg KH
2005-11-15  6:31         ` Coywolf Qi Hunt
2005-11-17 13:54         ` Pavel Machek
2005-11-15 14:42 ` Andi Kleen
2005-11-15 17:33   ` Greg KH
2005-11-16  8:12     ` Michael Kerrisk
2005-11-17  6:56       ` Greg KH
2005-11-17 12:12         ` Michael Kerrisk [this message]
2005-11-15 20:10 ` Luca
2005-11-15 20:13   ` Josh Boyer
2005-11-15 20:56   ` Greg KH
2005-11-16  4:38     ` Randy.Dunlap
2005-11-15 22:20   ` sitexec
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 12:15 linux

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=3210.1132229551@www25.gmx.net \
    --to=mtk-manpages@gmx.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk-lkml@gmx.net \
    /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