From: Paul Mundt <lethal@linux-sh.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] sh updates for 2.6.37-rc6
Date: Tue, 14 Dec 2010 10:05:47 +0000 [thread overview]
Message-ID: <20101214100547.GH14606@linux-sh.org> (raw)
Not much of note here. A missing syscall for non-multiplexed socketcalls,
and we've temporarily re-enabled the deprecated IRQ chip APIs to give the
MFD and GPIO drivers a chance to catch up in .38 as requested by Mark Brown.
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/lethal/sh-2.6.git sh-fixes-for-linus
Which contains:
Carmelo AMOROSO (1):
sh: wire up accept4 syscall (non-multiplexed path)
Paul Mundt (1):
sh: Enable deprecated IRQ chip APIs for MFD and GPIOLIB drivers.
arch/sh/Kconfig | 3 ++-
arch/sh/include/asm/unistd_32.h | 3 ++-
arch/sh/kernel/syscalls_32.S | 1 +
3 files changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2010-12-14 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 10:05 Paul Mundt [this message]
2010-12-14 11:08 ` [GIT PULL] sh updates for 2.6.37-rc6 Mark Brown
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=20101214100547.GH14606@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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