From: Greg Ungerer <gerg@linux-m68k.org>
To: torvalds@linux-foundation.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
gerg@kernel.org
Subject: [git pull] m68knommu fixes for v7.2
Date: Sun, 12 Jul 2026 22:46:24 +1000 [thread overview]
Message-ID: <608d7d1f-8e13-45fc-9546-2b2bd69707e7@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu git tree, m68knommu-fixes-on-top-off-7.2-rc2 tag.
There is only a single commit that fixes breakage introduced by changes
in the most recent merge window. The change fixes incorrectly updated
local SoC IO access function names. Testing didn't pick them up because
there was no specific defconfig for these particular SoC parts. New
defconfigs will be introduced in next merge cycle to remedy that.
Regards
Greg
The following changes since commit 8cdeaa50eae8dad34885515f62559ee83e7e8dda:
Linux 7.2-rc2 (2026-07-05 14:44:06 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-fixes-on-top-off-7.2-rc2
for you to fetch changes up to f47b6b313df9a17010a72b3f389f0a5e9e49db3b:
m68k: coldfire: fix breakage of missed IO access updates (2026-07-08 22:51:54 +1000)
----------------------------------------------------------------
m68knommu: fix on top off v7.2-rc2
. fix broken local SoC IO accesses
----------------------------------------------------------------
Greg Ungerer (1):
m68k: coldfire: fix breakage of missed IO access updates
arch/m68k/coldfire/m523x.c | 2 +-
arch/m68k/coldfire/m528x.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2026-07-12 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 12:46 Greg Ungerer [this message]
2026-07-12 19:13 ` 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=608d7d1f-8e13-45fc-9546-2b2bd69707e7@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=gerg@kernel.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