From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 00/10] [GIT PULL] tracing: various fixes
Date: Mon, 5 Dec 2011 10:47:18 +0100 [thread overview]
Message-ID: <20111205094718.GA9614@elte.hu> (raw)
In-Reply-To: <1323045081.19933.79.camel@pippen.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 2011-12-03 at 10:20 +0100, Ingo Molnar wrote:
>
> > Hm, not all were regression fixes and the branch was named
> > */core so i took it into perf/core.
>
> Yeah it happened just at the end of the merge window. I didn't really
> know what branch to name it.
>
> >
> > Could you perhaps cherry-pick the most crutial regression
> > fixes into an urgent branch? We could still push that
> > upstream.
>
> Looking at each patch, I would say 6 of the ten need to go in.
> Most are marked as stable since they break the last tree. I
> could just send them all to stable if it seems strange to have
> this many patches in two pull requests.
We can cherry-pick those 6 patches into perf/urgent - just make
sure you merge the cherry-picked branch into your devel branch
before adding new changes to the same files, there will be tons
of conflicts otherwise.
Thanks,
Ingo
prev parent reply other threads:[~2011-12-05 9:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 1:29 [PATCH 00/10] [GIT PULL] tracing: various fixes Steven Rostedt
2011-11-08 1:29 ` [PATCH 01/10] tracing: fix event_subsystem ref counting Steven Rostedt
2011-11-08 1:29 ` [PATCH 02/10] tracing: Restore system filter behavior Steven Rostedt
2011-11-08 1:29 ` [PATCH 03/10] tracing: Add boiler plate for subsystem filter Steven Rostedt
2011-11-08 1:29 ` [PATCH 04/10] tracing: update Documentation on max preds limit Steven Rostedt
2011-11-08 1:29 ` [PATCH 05/10] lockdep: Show subclass in pretty print of lockdep output Steven Rostedt
2011-11-08 1:29 ` [PATCH 06/10] ftrace: Remove force undef config value left for testing Steven Rostedt
2011-11-08 1:29 ` [PATCH 07/10] jump_label: jump_label_inc may return before the code is patched Steven Rostedt
2011-11-08 1:29 ` [PATCH 08/10] perf: Fix parsing of __print_flags() in TP_printk() Steven Rostedt
2011-11-08 1:29 ` [PATCH 09/10] ftrace: Fix hash record accounting bug Steven Rostedt
2011-11-08 1:29 ` [PATCH 10/10] tracing/latency: Fix header output for latency tracers Steven Rostedt
2011-11-11 8:33 ` [PATCH 00/10] [GIT PULL] tracing: various fixes Ingo Molnar
2011-11-29 21:33 ` Steven Rostedt
2011-12-03 9:20 ` Ingo Molnar
2011-12-05 0:31 ` Steven Rostedt
2011-12-05 9:47 ` Ingo Molnar [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=20111205094718.GA9614@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox