From: Robert Richter <robert.richter@amd.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: oprofile-list <oprofile-list@lists.sourceforge.net>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Oprofile kernel git tree
Date: Tue, 14 Oct 2008 15:56:45 +0200 [thread overview]
Message-ID: <20081014135645.GF23557@erda.amd.com> (raw)
In-Reply-To: <87r66kqlpt.fsf@basil.nowhere.org>
On 13.10.08 22:33:18, Andi Kleen wrote:
> Robert Richter <robert.richter@amd.com> writes:
> >
> > Feature branches (patches not yet ready for upstream, fast-forward only):
> >
> > arch-perfmon
>
> What do you mean with that? arch-perfmon is definitely ready for upstream.
This contains only the patch I wrote that changes the
initialization. All other patches are already in the upstream branch.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2008-10-14 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 20:20 Oprofile kernel git tree Robert Richter
2008-10-13 20:33 ` Andi Kleen
2008-10-14 13:56 ` Robert Richter [this message]
2008-10-14 14:10 ` 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=20081014135645.GF23557@erda.amd.com \
--to=robert.richter@amd.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sourceforge.net \
--cc=paulus@samba.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