From: Andrew Morton <akpm@osdl.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: mikpe@csd.uu.se, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][1/6] perfctr-2.7.3 for 2.6.7-rc1-mm1: core
Date: Tue, 22 Jun 2004 12:22:54 -0700 [thread overview]
Message-ID: <20040622122254.10bf8ff7.akpm@osdl.org> (raw)
In-Reply-To: <16600.15183.989137.233305@alkaid.it.uu.se>
Mikael Pettersson <mikpe@csd.uu.se> wrote:
>
> > We need (especially at this stage in the kernel cycle) at least a couple of
> > pages of design documentation which describes
>
> Speaking of documentation, I have a strong preference for using
> LaTeX for all papers, reports, docs, etc, except man pages.
> Is that an acceptable format?
Sounds fine, but excessive for this exercise. At this stage I'm asking for
sufficient description of the kernel patch to allow other developers to
understand and review the patch, maybe hack on it a bit. A couple of pages
of ascii should suffice. I'd consider it compulsory for patches of this
magnitude and scope.
Longer term, yes - having added a bunch of new syscalls to the kernel we
have a responsibility to document the user/kernel API for downstream users,
but that's not a requirement for reviewing the patch.
next prev parent reply other threads:[~2004-06-22 19:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-31 22:18 Mikael Pettersson
2004-06-22 8:53 ` Andrew Morton
2004-06-22 8:59 ` Christoph Hellwig
2004-06-22 9:04 ` Andrew Morton
2004-06-22 9:12 ` Christoph Hellwig
2004-06-22 9:14 ` Andrew Morton
2004-06-22 9:18 ` Christoph Hellwig
2004-06-22 9:20 ` Andrew Morton
2004-06-22 14:38 ` Mikael Pettersson
2004-06-22 17:20 ` Christoph Hellwig
2004-06-22 20:35 ` Mikael Pettersson
2004-06-22 13:47 ` Mikael Pettersson
2004-06-22 19:18 ` Andrew Morton
2004-06-22 13:59 ` Mikael Pettersson
2004-06-22 19:22 ` Andrew Morton [this message]
[not found] <223si-461-9@gated-at.bofh.it>
[not found] ` <29Piu-4H4-27@gated-at.bofh.it>
2004-06-22 10:21 ` Andi Kleen
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=20040622122254.10bf8ff7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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