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 5.9
Date: Mon, 3 Aug 2020 13:30:04 +0200 [thread overview]
Message-ID: <20200803113004.10098-1-geert@linux-m68k.org> (raw)
Hi Linus,
The following changes since commit 9ebcfadb0610322ac537dd7aa5d9cbc2b2894c68:
Linux 5.8-rc3 (2020-06-28 15:00:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git tags/m68k-for-v5.9-tag1
for you to fetch changes up to 382f429bb559fe991b1ece2e5e58c812e28b3ad8:
m68k: defconfig: Update defconfigs for v5.8-rc3 (2020-07-13 11:41:52 +0200)
----------------------------------------------------------------
m68k updates for v5.9
- Several Kbuild improvements,
- Several Mac fixes,
- Minor cleanups and fixes,
- Defconfig updates.
Note that the base is v5.8-rc3, due to late Kconfig changes impacting
the defconfigs.
Thanks for pulling!
----------------------------------------------------------------
Finn Thain (4):
m68k: mac: Don't send IOP message until channel is idle
m68k: mac: Fix IOP status/control register writes
m68k: mac: Don't send uninitialized data in IOP message reply
m68k: mac: Improve IOP debug messages
Geert Uytterhoeven (1):
m68k: defconfig: Update defconfigs for v5.8-rc3
Gustavo A. R. Silva (1):
m68k: Use sizeof_field() helper
Masahiro Yamada (5):
m68k: Add arch/m68k/Kbuild
m68k: sun3: Descend to prom from arch/m68k/sun3
m68k: Optimize cc-option calls for cpuflags-y
m68k: Pass -D options to KBUILD_CPPFLAGS instead of KBUILD_{A,C}FLAGS
m68k: Use CLEAN_FILES to clean up files
Michael Schmitz (1):
m68k: atari: Annotate dummy read in ROM port IO code as __maybe_unused
arch/m68k/Kbuild | 19 ++++++++++
arch/m68k/Makefile | 73 ++++++++++++++----------------------
arch/m68k/configs/amiga_defconfig | 3 ++
arch/m68k/configs/apollo_defconfig | 3 ++
arch/m68k/configs/atari_defconfig | 3 ++
arch/m68k/configs/bvme6000_defconfig | 3 ++
arch/m68k/configs/hp300_defconfig | 3 ++
arch/m68k/configs/mac_defconfig | 3 ++
arch/m68k/configs/multi_defconfig | 3 ++
arch/m68k/configs/mvme147_defconfig | 3 ++
arch/m68k/configs/mvme16x_defconfig | 3 ++
arch/m68k/configs/q40_defconfig | 3 ++
arch/m68k/configs/sun3_defconfig | 3 ++
arch/m68k/configs/sun3x_defconfig | 3 ++
arch/m68k/include/asm/raw_io.h | 6 +--
arch/m68k/kernel/signal.c | 32 ++++++++--------
arch/m68k/mac/iop.c | 60 +++++++++++++----------------
arch/m68k/sun3/Makefile | 2 +-
18 files changed, 129 insertions(+), 99 deletions(-)
create mode 100644 arch/m68k/Kbuild
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:[~2020-08-03 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 11:30 Geert Uytterhoeven [this message]
2020-08-03 21:25 ` 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=20200803113004.10098-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®