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 more fixes for v7.2
Date: Sun, 26 Jul 2026 23:35:21 +1000 [thread overview]
Message-ID: <376ae320-2b14-49bf-a296-a0cc01b93b78@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu git tree, m68knommu-fixes-on-top-off-7.2-rc4 tag.
There is only a single commit that fixes more breakage introduced by
ColdFire IO access changes in the most recent merge window. The change
fixes an IO access call site that was missed.
Regards
Greg
The following changes since commit 1590cf0329716306e948a8fc29f1d3ee87d3989f:
Linux 7.2-rc4 (2026-07-19 13:54:41 -0700)
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-rc4
for you to fetch changes up to 41e116ad01d8a704883187743b52d57e11bc3ef0:
m68k: coldfire: fix breakage of missed IO access update (2026-07-20 10:20:53 +1000)
----------------------------------------------------------------
m68knommu: fix on top off v7.2-rc4
. fix broken local SoC IO accesses for ColdFire
----------------------------------------------------------------
Greg Ungerer (1):
m68k: coldfire: fix breakage of missed IO access update
arch/m68k/coldfire/m528x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2026-07-26 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 13:35 Greg Ungerer [this message]
2026-07-26 20:00 ` 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=376ae320-2b14-49bf-a296-a0cc01b93b78@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
all inboxes | Powered by JetHome®