From: Paul Mundt <lethal@linux-sh.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] sh updates for 2.6.32-rc5
Date: Wed, 14 Oct 2009 09:06:31 +0000 [thread overview]
Message-ID: <20091014090630.GA29807@linux-sh.org> (raw)
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git sh/for-2.6.32
Which contains:
Paul Mundt (8):
sh: update die() output.
sh: force dcache flush if dcache_dirty bit set.
sh: ftrace: Fix up syscall tracepoint support.
sh: Use boot_cpu_data for FPU tests in sigcontext paths.
sh: Tidy up SMP cpuinfo.
sh: Populate initial secondary CPU info from boot_cpu_data.
sh: Optimize the setup_rt_frame() I-cache flush.
sh: Fix a TRACE_IRQS_OFF typo.
arch/sh/kernel/entry-common.S | 2 +-
arch/sh/kernel/ftrace.c | 37 +++++++++++++++++++++++++++----------
arch/sh/kernel/setup.c | 2 ++
arch/sh/kernel/signal_32.c | 9 ++++-----
arch/sh/kernel/smp.c | 2 ++
arch/sh/kernel/traps_32.c | 7 ++++---
arch/sh/mm/cache.c | 2 +-
7 files changed, 41 insertions(+), 20 deletions(-)
reply other threads:[~2009-10-14 9:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091014090630.GA29807@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=torvalds@linux-foundation.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).