From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/2 v2] [GIT PULL] tracing: updates for 3.5
Date: Fri, 27 Apr 2012 17:09:02 -0700 [thread overview]
Message-ID: <4F9B351E.1000205@linux.intel.com> (raw)
In-Reply-To: <1335571592.28106.240.camel@gandalf.stny.rr.com>
On 04/27/2012 05:06 PM, Steven Rostedt wrote:
> On Fri, 2012-04-27 at 11:14 -0700, H. Peter Anvin wrote:
>> On 04/26/2012 06:54 PM, Steven Rostedt wrote:
>>>
>>> Peter,
>>>
>>> I just realized that these two patches contained a Cc to you, but the
>>> cover letter did not Cc you. Probably confused you in what to pull.
>>>
>>> Sorry about that.
>>>
>>
>> Joy. Let me figure out the remaining patches and pull them in.
>>
>
> Do you want me to rebase on top of tip, and do another pull request.
> That may make it easier on you.
>
Sure.
-hpa
prev parent reply other threads:[~2012-04-28 0:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 17:34 [PATCH 0/2 v2] [GIT PULL] tracing: updates for 3.5 Steven Rostedt
2012-04-26 17:34 ` [PATCH 1/2 v2] ftrace/x86: Have arch x86_64 use breakpoints instead of stop machine Steven Rostedt
2012-04-26 19:43 ` [tip:x86/ftrace] ftrace, x86: " tip-bot for Steven Rostedt
2012-04-27 1:33 ` [PATCH 1/2 v2] ftrace/x86: " Masami Hiramatsu
2012-04-26 17:34 ` [PATCH 2/2 v2] ftrace/x86: Remove the complex ftrace NMI handling code Steven Rostedt
2012-04-26 19:44 ` [tip:x86/ftrace] ftrace, x86: " tip-bot for Steven Rostedt
2012-04-27 1:46 ` [PATCH 0/2 v2] [GIT PULL] tracing: updates for 3.5 Steven Rostedt
2012-04-27 1:54 ` Steven Rostedt
2012-04-27 18:14 ` H. Peter Anvin
2012-04-28 0:06 ` Steven Rostedt
2012-04-28 0:09 ` H. Peter Anvin [this message]
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=4F9B351E.1000205@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.