From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg Ungerer <gerg@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [GIT PULL] m68k updates for v5.15 (take three)
Date: Tue, 28 Sep 2021 16:00:18 +0200 [thread overview]
Message-ID: <20210928140018.2441795-1-geert@linux-m68k.org> (raw)
Hi Linus,
The following changes since commit a7b68ed15d1fd72c1e451d5eb6edebee2a624b90:
m68k: mvme: Remove overdue #warnings in RTC handling (2021-09-13 11:19:05 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git tags/m68k-for-v5.15-tag3
for you to fetch changes up to 9fde0348640252c79d462c4d29a09a14e8741f5c:
m68k: Remove set_fs() (2021-09-24 13:35:07 +0200)
----------------------------------------------------------------
m68k updates for v5.15 (take three)
- Signal handling fixes,
- Removal of set_fs().
Thanks for pulling!
----------------------------------------------------------------
Al Viro (3):
m68k: Handle arrivals of multiple signals correctly
m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal
m68k: Leave stack mangling to asm wrapper of sigreturn()
Christoph Hellwig (6):
m68k: Document that access_ok is broken for !CONFIG_CPU_HAS_ADDRESS_SPACES
m68k: Remove the 030 case in virt_to_phys_slow
m68k: Use BUILD_BUG for passing invalid sizes to get_user/put_user
m68k: Factor the 8-byte lowlevel {get,put}_user code into helpers
m68k: Provide __{get,put}_kernel_nofault
m68k: Remove set_fs()
arch/m68k/68000/entry.S | 4 -
arch/m68k/Kconfig | 1 -
arch/m68k/coldfire/entry.S | 4 -
arch/m68k/include/asm/processor.h | 31 +++++-
arch/m68k/include/asm/segment.h | 59 ----------
arch/m68k/include/asm/thread_info.h | 3 -
arch/m68k/include/asm/tlbflush.h | 11 +-
arch/m68k/include/asm/traps.h | 4 +
arch/m68k/include/asm/uaccess.h | 215 +++++++++++++++++++++++-------------
arch/m68k/kernel/asm-offsets.c | 2 +-
arch/m68k/kernel/entry.S | 58 +++++-----
arch/m68k/kernel/process.c | 4 +-
arch/m68k/kernel/signal.c | 199 ++++++++++++++-------------------
arch/m68k/kernel/traps.c | 13 +--
arch/m68k/mac/misc.c | 1 -
arch/m68k/mm/cache.c | 25 +----
arch/m68k/mm/init.c | 6 -
arch/m68k/mm/kmap.c | 1 -
arch/m68k/mm/memory.c | 1 -
arch/m68k/mm/motorola.c | 2 +-
arch/m68k/sun3/config.c | 3 +-
arch/m68k/sun3/mmu_emu.c | 6 +-
arch/m68k/sun3/sun3ints.c | 1 -
arch/m68k/sun3x/prom.c | 1 -
24 files changed, 301 insertions(+), 354 deletions(-)
delete mode 100644 arch/m68k/include/asm/segment.h
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:[~2021-09-28 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 14:00 Geert Uytterhoeven [this message]
2021-09-28 20:29 ` pr-tracker-bot
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=20210928140018.2441795-1-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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®