From: Mikael Pettersson <mikpe@csd.uu.se>
To: Andrew Morton <akpm@osdl.org>
Cc: Mikael Pettersson <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 15:59:43 +0200 [thread overview]
Message-ID: <16600.15183.989137.233305@alkaid.it.uu.se> (raw)
In-Reply-To: <20040622015311.561a73bf.akpm@osdl.org>
Andrew Morton writes:
> Mikael Pettersson <mikpe@csd.uu.se> wrote:
> >
> > perfctr-2.7.3 for 2.6.7-rc1-mm1, part 1/6:
> >
>
> OK, I spent a couple hours on the perfctr code. It looks sane, although a
> bit hard to follow. The above changelog (which is _all_ you gave us) makes
> this large and complex patch hard to review, hard to understand, hard for
> others to support.
>
> One can look at the code, sort-of-see what it's doing, query micro-issues,
> but it is hard (and a bad use of one's time) to try and reverse-engineer
> the big-picture "how it all hangs together" from the implementation.
>
> 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?
next prev parent reply other threads:[~2004-06-22 14:13 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 [this message]
2004-06-22 19:22 ` Andrew Morton
[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=16600.15183.989137.233305@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®