public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: eranian@hpl.hp.com
Cc: perfmon@napali.hpl.hp.com, perfctr-devel@lists.sourceforge.net,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	oprofile-list@lists.sourceforge.net
Subject: Re: 2.6.18 perfmon new code base + libpfm + pfmon
Date: Wed, 27 Sep 2006 05:09:51 +0000	[thread overview]
Message-ID: <20060926220951.39bd344f.akpm@osdl.org> (raw)
In-Reply-To: <20060926143420.GF14550@frankl.hpl.hp.com>

On Tue, 26 Sep 2006 07:34:20 -0700
Stephane Eranian <eranian@hpl.hp.com> wrote:

> I have released another version of the perfmon new code base package.
> This version of the kernel patch is relative to 2.6.18. This longer
> than usual delay between releases comes from the large amount of changes
> than went into this new release following the feedback I got on LKML. As
> a result, the code has improved.

Thanks for doing that.

Would it be possible to get an accounting of the disposition of the various
review comments?  Of the "yes I did that" or "OK, but I'll do it later" or
"no, you're an idiot" form?



  reply	other threads:[~2006-09-27  5:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 14:34 2.6.18 perfmon new code base + libpfm + pfmon Stephane Eranian
2006-09-27  5:09 ` Andrew Morton [this message]
2006-09-27 22:48   ` Stephane Eranian
2006-09-27 23:31     ` Andrew Morton
2006-09-28  6:49       ` Stephane Eranian
2006-09-28  7:05         ` Andrew Morton
2006-09-28  7:32     ` Andi Kleen
2006-09-28  7:56       ` Stephane Eranian
2006-09-28  8:05         ` Andi Kleen
2006-09-29  9:30           ` Stephane Eranian
2006-09-28 13:41     ` Christoph Hellwig
2006-09-28 14:04       ` Stephane Eranian

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=20060926220951.39bd344f.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=perfctr-devel@lists.sourceforge.net \
    --cc=perfmon@napali.hpl.hp.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