From: "stephane eranian" <eranian@googlemail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Jesse Barnes" <jbarnes@virtuousgeek.org>,
"David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [patch 00/24] perfmon3: introduction
Date: Thu, 23 Oct 2008 09:19:06 +0200 [thread overview]
Message-ID: <7c86c4470810230019g65bce230yfc0c86cc55056e34@mail.gmail.com> (raw)
In-Reply-To: <20081022102257.60dc8d08.akpm@linux-foundation.org>
Andrew,
On Wed, Oct 22, 2008 at 7:22 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Wed, 22 Oct 2008 09:58:22 -0700 Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
> It is several years late. For me the problem has been that we do a lot
> of review and have lots of discussion but then the trail goes cold for
> six months and when it all pops up again the code has changed and/or
> we've all forgotten about it again.
>
The kind of changes I have made following ealier reviews are not trivial,
It takes time and I do other things as well. So I could not really post on
LKML every week with something that would work and be worthy of
your time.
> What it needs is a sustained effort to get it over the hump. How's
> about getting it into linux-next asap and then we all agree to do the
> re-re-re-review and runtime testing for a 2.6.29 merge?
>
Let's do this, then.
Thanks.
next prev parent reply other threads:[~2008-10-23 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:05 eranian
2008-10-22 4:25 ` David Miller
2008-10-22 8:39 ` stephane eranian
2008-10-22 16:58 ` Jesse Barnes
2008-10-22 17:22 ` Andrew Morton
2008-10-23 7:19 ` stephane eranian [this message]
2008-11-10 2:41 ` Paul Mackerras
2008-11-10 15:24 ` stephane eranian
2008-11-11 0:29 ` 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=7c86c4470810230019g65bce230yfc0c86cc55056e34@mail.gmail.com \
--to=eranian@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®