From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-m68k@lists.linux-m68k.org
Subject: [PATCH 0/3] m68k: Allow all kernel traps to be handled via exception fixups
Date: Fri, 7 Jan 2011 17:22:02 +0100 [thread overview]
Message-ID: <1294417325-6109-1-git-send-email-geert@linux-m68k.org> (raw)
This patch series is a split and cleanup of the single commit
aa8fcffdec0ac8d0ace3af622eb92f5ee804fc44
("m68k-allow-all-kernel-traps-to-be-handled-via-exception-fixups-all.diff"),
which dates back to the Linux/m68k CVS tree.
It's a prerequisite for ARAnyM support.
[PATCH 1/3] m68k: Add helper function handle_kernel_fault()
[PATCH 2/3] m68k: Use base_trap_init() to initialize vectors
[PATCH 3/3] m68k: Allow all kernel traps to be handled via exception fixups
arch/m68k/kernel/traps.c | 10 +++++++---
b/arch/m68k/include/asm/processor.h | 2 ++
b/arch/m68k/kernel/signal.c | 24 +++++++++++++++++++++++-
b/arch/m68k/kernel/traps.c | 10 +++++-----
b/arch/m68k/mm/fault.c | 16 +---------------
5 files changed, 38 insertions(+), 24 deletions(-)
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
next reply other threads:[~2011-01-07 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 16:22 Geert Uytterhoeven [this message]
2011-01-07 16:22 ` [PATCH 1/3] m68k: Add helper function handle_kernel_fault() Geert Uytterhoeven
2011-01-07 16:22 ` [PATCH 2/3] m68k: Use base_trap_init() to initialize vectors Geert Uytterhoeven
2011-01-07 16:22 ` [PATCH 3/3] m68k: Allow all kernel traps to be handled via exception fixups Geert Uytterhoeven
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=1294417325-6109-1-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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