public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
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.10
Date: Mon, 12 Oct 2020 14:09:04 +0200	[thread overview]
Message-ID: <20201012120904.12998-1-geert@linux-m68k.org> (raw)

	Hi Linus,

The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:

  Linux 5.9-rc1 (2020-08-16 13:04:57 -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.10-tag1

for you to fetch changes up to 50c5feeea0af99a4401fd54fd72bec1333a496ca:

  ide/macide: Convert Mac IDE driver to platform driver (2020-09-28 10:48:17 +0200)

----------------------------------------------------------------
m68k updates for v5.10

  - Conversion of the Mac IDE driver to a platform driver,
  - Minor cleanups and fixes.

Thanks for pulling!

----------------------------------------------------------------
Alexander A. Klimov (1):
      m68k: Replace HTTP links with HTTPS ones

Christoph Hellwig (1):
      m68k: Use get_kernel_nofault() in show_registers()

Finn Thain (2):
      m68k: Correct some typos in comments
      ide/macide: Convert Mac IDE driver to platform driver

Geert Uytterhoeven (7):
      m68k: amiga: Fix Denise detection on OCS
      zorro: Fix address space collision message with RAM expansion boards
      m68k: Revive _TIF_* masks
      m68k: amiga: Clean up Amiga hardware configuration
      m68k: Sort selects in main Kconfig
      m68k: mm: Use PAGE_ALIGNED() helper
      m68k: mm: Remove superfluous memblock_alloc*() casts

 arch/m68k/Kconfig                   |  24 ++++----
 arch/m68k/amiga/config.c            | 118 ++++++++++++++++++------------------
 arch/m68k/configs/mac_defconfig     |   1 +
 arch/m68k/configs/multi_defconfig   |   1 +
 arch/m68k/include/asm/thread_info.h |   8 +++
 arch/m68k/kernel/head.S             |  16 ++---
 arch/m68k/kernel/traps.c            |   5 +-
 arch/m68k/mac/config.c              |  41 +++++++++++++
 arch/m68k/mac/macboing.c            |   2 +-
 arch/m68k/mm/mcfmmu.c               |   2 +-
 arch/m68k/mm/motorola.c             |   9 ++-
 drivers/ide/Kconfig                 |   7 ++-
 drivers/ide/macide.c                |  66 +++++++++++++-------
 drivers/zorro/zorro.c               |   2 +-
 14 files changed, 184 insertions(+), 118 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

             reply	other threads:[~2020-10-12 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 12:09 Geert Uytterhoeven [this message]
2020-10-12 18:21 ` [GIT PULL] m68k updates for 5.10 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=20201012120904.12998-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