From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
oprofile-list <oprofile-list@lists.sourceforge.net>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] oprofile: updates for v2.6.34
Date: Tue, 9 Mar 2010 12:27:52 +0100 [thread overview]
Message-ID: <20100309112752.GG3650@erda.amd.com> (raw)
In-Reply-To: <20100304174422.GQ13205@erda.amd.com>
On 04.03.10 18:44:22, Robert Richter wrote:
> On 04.03.10 11:50:05, Ingo Molnar wrote:
> >
> > * Robert Richter <robert.richter@amd.com> wrote:
> >
> > > Ingo,
> > >
> > > it's only one patch, please pull from:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git urgent
> > >
> > > (It seems the git mirror is not yet sync'ed.)
> >
> > Still cannot pull - forgot to push out?
>
> No, it is already out, at least it is available now:
>
> http://git.kernel.org/?p=linux/kernel/git/rric/oprofile.git;a=shortlog;h=refs/heads/urgent
Ingo,
can you try to send that one patch in urgent upstream for .34? It is
already in the queue for 1 week.
Could you also pull the oprofile core tree with the reservation code
to tip/oprofile? I also want to merge this to perf/core after pending
perf patches esp. pebs are applied to tip. When do you think perf/core
can be updated?
Thanks,
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2010-03-09 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 16:44 [GIT PULL] oprofile: updates for v2.6.34 Robert Richter
2010-03-04 10:50 ` Ingo Molnar
2010-03-04 17:44 ` Robert Richter
2010-03-09 11:27 ` Robert Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-04 10:47 Robert Richter
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=20100309112752.GG3650@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sourceforge.net \
--cc=peterz@infradead.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