From: Steven Rostedt <rostedt@goodmis.org>
To: David Rientjes <rientjes@google.com>
Cc: Hirokazu Takata <takata@linux-m32r.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/2] [GIT PULL][v3.2] tracing: various fixes
Date: Mon, 17 Oct 2011 20:09:49 -0400 [thread overview]
Message-ID: <1318896589.4722.17.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1110171424270.18439@chino.kir.corp.google.com>
On Mon, 2011-10-17 at 14:26 -0700, David Rientjes wrote:
> On Mon, 17 Oct 2011, Steven Rostedt wrote:
>
> > > I could add it, but we should have an Acked-by from Hirokazu Takata.
> >
> >
> > Here's the patch I'm referring to:
> >
> > https://lkml.org/lkml/2011/10/13/259
> >
> > Thanks!
> >
>
> This patch makes my m32r cross-compiler happy, so for that:
>
> Acked-by: David Rientjes <rientjes@google.com>
>
> although the "Link:" field in that patch doesn't work for me.
OK, I'll add it with your Ack and a Cc to Hirokazu.
As for the link, it will work again when kernel.org has that operational
again.
The Link: format is:
Link: http://lkml.kernel.org/r/<message-id>
You can also find this at:
http://marc.info/?i=<message-id>
which would give you:
http://marc.info/?i=20111013085936.GA13046@elte.hu
-- Steve
next prev parent reply other threads:[~2011-10-18 0:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 17:49 Steven Rostedt
2011-10-17 17:49 ` [PATCH 1/2] ftrace: Fix README to state tracing_on to start/stop tracing Steven Rostedt
2011-10-17 17:49 ` [PATCH 2/2] tracing: Fix returning of duplicate data after EOF in trace_pipe_raw Steven Rostedt
2011-10-17 18:54 ` [PATCH 0/2] [GIT PULL][v3.2] tracing: various fixes Ingo Molnar
2011-10-17 19:10 ` Steven Rostedt
2011-10-17 19:40 ` Ingo Molnar
2011-10-17 20:05 ` Steven Rostedt
2011-10-17 20:12 ` Steven Rostedt
2011-10-17 21:26 ` David Rientjes
2011-10-18 0:09 ` Steven Rostedt [this message]
2011-10-18 3:16 ` Hirokazu Takata
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=1318896589.4722.17.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=takata@linux-m32r.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®