From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Roland McGrath <roland@redhat.com>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: [PATCH 0/3 v2] [GIT PULL] remove unlikelys
Date: Wed, 25 Mar 2009 11:45:38 -0400 [thread overview]
Message-ID: <20090325154538.916038098@goodmis.org> (raw)
Ingo,
The differences between v1 and v2 is that I only included the non
controversial patches. I also modified the change log of pre_schedule_rt
to include the annotated branch profiler output.
I just did a force push, so please use ssh, or verify that only these
three patches are present.
Thanks,
-- Steve
Please pull the latest annotate-branch/cleanups tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
annotate-branch/cleanups
Steven Rostedt (3):
sched: remove unlikely in pre_schedule_rt
sched: remove unlikelys from sched_move_task
mm: remove unlikelys for unlock in rmap.c
----
kernel/sched.c | 4 ++--
kernel/sched_rt.c | 2 +-
mm/rmap.c | 8 ++++----
3 files changed, 7 insertions(+), 7 deletions(-)
--
next reply other threads:[~2009-03-25 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 15:45 Steven Rostedt [this message]
2009-03-25 15:45 ` [PATCH 1/3 v2] sched: remove unlikely in pre_schedule_rt Steven Rostedt
2009-03-25 15:45 ` [PATCH 2/3 v2] sched: remove unlikelys from sched_move_task Steven Rostedt
2009-03-25 15:45 ` [PATCH 3/3 v2] mm: remove unlikelys for unlock in rmap.c Steven Rostedt
2009-03-25 15:49 ` [PATCH 0/3 v2] [GIT PULL] remove unlikelys Steven Rostedt
2009-03-25 16:19 ` Ingo Molnar
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=20090325154538.916038098@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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