From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg Ungerer <gerg@uclinux.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: [git pull] m68k updates for 2.6.38
Date: Mon, 10 Jan 2011 20:58:59 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.00.1101082222060.25612@ayla.of.borg> (raw)
Hi Linus,
The following changes since commit 3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5:
Linus Torvalds (1):
Linux 2.6.37
are available in the git repository at:
master.kernel.org:/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus
The m68knommu changes have been acked by Greg Ungerer.
Al Viro (16):
m68k: Resetting sa_handler in local copy of k_sigaction is pointless
m68k: Switch to saner sigsuspend()
m68k: Simplify the singlestepping handling in signals
m68k: Don't lose state if sigframe setup fails
m68k: If we fail to set sigframe up, just leave regs alone...
m68k: Fix stack mangling logics in sigreturn
m68k: Missing syscall_trace() on sigreturn
m68k: Check __get_user()/__put_user() return value
m68knommu: Don't bother with SA_ONESHOT
m68knommu: Switch to saner sigsuspend
m68knommu: Handle multiple pending signals
m68knommu: Don't lose state if sigframe setup fails
m68knommu: f_pcr has been gone since headers' merge
m68knommu: Equivalent of "m68k: handle new gcc's"
m68knommu: signal.c __user annotations
m68knommu: Need to check __get_user()/__put_user() result
Geert Uytterhoeven (1):
m68k/sun3: Kill pte_unmap() warnings
arch/m68k/include/asm/sun3_pgtable.h | 5 +-
arch/m68k/include/asm/thread_info.h | 1 +
arch/m68k/include/asm/unistd.h | 1 +
arch/m68k/kernel/entry.S | 30 +---
arch/m68k/kernel/signal.c | 314 +++++++++++++-----------------
arch/m68knommu/kernel/entry.S | 16 --
arch/m68knommu/kernel/signal.c | 188 ++++++++----------
arch/m68knommu/platform/68328/entry.S | 7 +-
arch/m68knommu/platform/68360/entry.S | 7 +-
arch/m68knommu/platform/coldfire/entry.S | 5 +-
10 files changed, 231 insertions(+), 343 deletions(-)
Thanks for pulling!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
reply other threads:[~2011-01-10 19:59 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=alpine.DEB.2.00.1101082222060.25612@ayla.of.borg \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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
all inboxes | Powered by JetHome®