From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Hirokazu Takata <takata@linux-m32r.org>
Subject: Re: [PATCH 0/2] [GIT PULL][v3.2] tracing: various fixes
Date: Mon, 17 Oct 2011 16:05:23 -0400 [thread overview]
Message-ID: <1318881923.4722.11.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20111017194030.GA6502@elte.hu>
On Mon, 2011-10-17 at 21:40 +0200, Ingo Molnar wrote:
> * Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Mon, 2011-10-17 at 20:54 +0200, Ingo Molnar wrote:
> >
> > > How about the m32r build fix? I think we should apply it to
> > > perf/core if everyone else was fine with your fix.
> >
> > Hmm, I saw a notice that Andrew pulled it into his -mm tree. Is it
> > going that way?
>
> No. It must go into perf/core to not open up a wide bisection
> breakage window. So please apply if it everyone is happy with it.
>
I could add it, but we should have an Acked-by from Hirokazu Takata.
I would also be interested in knowing if the latest kernel is running on
any m32r hardware at the moment? There doesn't look to be much
development on the m32r arch.
-- Steve
next prev parent reply other threads:[~2011-10-17 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 17:49 [PATCH 0/2] [GIT PULL][v3.2] tracing: various fixes 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 [this message]
2011-10-17 20:12 ` Steven Rostedt
2011-10-17 21:26 ` David Rientjes
2011-10-18 0:09 ` Steven Rostedt
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=1318881923.4722.11.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=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;
as well as URLs for NNTP newsgroup(s).