mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
	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: Thu, 26 Apr 2012 21:54:49 -0400	[thread overview]
Message-ID: <1335491689.28106.192.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1335491171.28106.190.camel@gandalf.stny.rr.com>

On Thu, 2012-04-26 at 21:46 -0400, Steven Rostedt wrote:
> Hi Peter,
> 
> I see you pulled in the patches individually instead of doing a git
> pull. But you missed the three patches that were in the previous pull
> request (that I only left out to not spam LKML as they were not
> changed). Also, without the git pull, it makes my repo out of sync with
> tip. As that is usually how I know what was pushed upstream or not.
> 
> -- Steve
> 
> 
> On Thu, 2012-04-26 at 13:34 -0400, Steven Rostedt wrote:
> > Ingo,
> > 
> > Although only two patches are in this, it really contains the 5 patches
> > that I pushed out earlier. As only patch 4/5 changed, instead of
> > spamming LKML with the same patches 1-3, I'm only reposting 4 and 5.
> > 
> > Patch 5 just came along for the ride (same as the previous post).
> > 
> > Patch 4 (here it's patch 1) was update as per Masami's suggestions (again).
> > 

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.

-- Steve




  reply	other threads:[~2012-04-27  1:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 17:34 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 [this message]
2012-04-27 18:14     ` H. Peter Anvin
2012-04-28  0:06       ` Steven Rostedt
2012-04-28  0:09         ` H. Peter Anvin

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=1335491689.28106.192.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@elte.hu \
    /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®