From: Jay Cliburn <jacliburn@bellsouth.net>
To: Paul Jackson <pj@sgi.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Randy Dunlap" <rdunlap@xenotime.net>, Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] doc: document the kernel-doc conventions for kernel hackers
Date: Sat, 31 May 2008 09:42:53 -0500 [thread overview]
Message-ID: <20080531094253.30ae975e@osprey.hogchain.net> (raw)
In-Reply-To: <20080530221941.28920.30102.sendpatchset@polaris-admin.engr.sgi.com>
On Fri, 30 May 2008 15:19:41 -0700
Paul Jackson <pj@sgi.com> wrote:
> From: Paul Jackson <pj@sgi.com>
>
> Provide documentation of the kernel-doc documentation conventions
> oriented to kernel hackers.
>
> Since I figure that there will be more people reading this
> kernel-doc-nano-HOWTO.txt file who are kernel developers focused
> on the rest of the kernel, than there will be readers of this
> file who are documentation developers extracting that embedded
> kernel-doc documentation, I have taken the liberty of making
> the new section added here:
>
> How to format kernel-doc comments
>
> the first section of the kernel-doc-nano-HOWTO.txt file.
>
> This first section is intended to introduce, motivate and
> provide basic usage of the kernel-doc mechanism for kernel
> hackers developing other portions of the kernel.
>
> Signed-off-by: Paul Jackson <pj@sgi.com>
> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
>
> ---
> Documentation/kernel-doc-nano-HOWTO.txt | 99
> ++++++++++++++++++++++++++++++++ 1 file changed, 99 insertions(+)
>
> --- linux-2.6.orig/Documentation/kernel-doc-nano-HOWTO.txt
> 2008-05-30 08:47:13.000000000 -0700 +++
> linux-2.6/Documentation/kernel-doc-nano-HOWTO.txt 2008-05-30
> 15:14:33.281447922 -0700 @@ -1,6 +1,105 @@ kernel-doc nano-HOWTO
> =====================
>
> +How to format kernel-doc comments
> +---------------------------------
> +
> +In order to provide an embedded, 'C' friendly, easy to maintain,
> +but consistent and extractable documentation of the functions and
> +data structures in the Linux kernel, the Linux kernel has adopted
> +a consistent style for documenting functions and their parameters,
> +and structures and their members.
> +
> +The format for this documentation is called the kernel-doc format.
> +It as documented in this Documentation/kernel-doc-nano-HOWTO.txt
s/as/is
next prev parent reply other threads:[~2008-05-31 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 22:19 Paul Jackson
2008-05-31 14:42 ` Jay Cliburn [this message]
2008-06-02 2:40 ` Paul Jackson
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=20080531094253.30ae975e@osprey.hogchain.net \
--to=jacliburn@bellsouth.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=rdunlap@xenotime.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
Powered by JetHome