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 changes for v7.0
Date: Mon, 16 Feb 2026 09:52:28 +1000 [thread overview]
Message-ID: <37cdaebf-2365-4994-b270-272d1f7d84af@linux-m68k.org> (raw)
Hi Linus,
Please pull the m68knommu git tree changes for v7.0.
It contains a small defconfig cleanup, more use of strscpy() over strcpy()
and a fix for unaligned memmove() specifically for original 68000 machines.
Regards
Greg
The following changes since commit 63804fed149a6750ffd28610c5c1c98cce6bd377:
Linux 6.19-rc7 (2026-01-25 14:11:24 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git tags/m68knommu-for-v7.0
for you to fetch changes up to a16ac6ca46d62bcbcbd7b01be0ef03fb39530d7b:
m68knommu: Replace deprecated strcpy with strscpy in init_ucsimm (2026-01-27 12:38:52 +1000)
----------------------------------------------------------------
m68knommu: updates and fixes for v7.0
. defconfig cleanup
. fix for legacy 68000 CPU memmove() of non-aligned pointers
. replace strcpy() with strscpy() for ucsimm target
----------------------------------------------------------------
Daniel Palmer (1):
m68k: nommu: fix memmove() with differently aligned src and dest for 68000
Lukas Bulwahn (1):
m68k: defconfig: Clean up references to non-existing configs
Thorsten Blum (1):
m68knommu: Replace deprecated strcpy with strscpy in init_ucsimm
arch/m68k/68000/ucsimm.c | 3 ++-
arch/m68k/configs/amcore_defconfig | 2 --
arch/m68k/configs/m5475evb_defconfig | 1 -
arch/m68k/configs/stmark2_defconfig | 1 -
arch/m68k/lib/memmove.c | 18 ++++++++++++++++++
5 files changed, 20 insertions(+), 5 deletions(-)
next reply other threads:[~2026-02-15 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 23:52 Greg Ungerer [this message]
2026-02-16 3:47 ` 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=37cdaebf-2365-4994-b270-272d1f7d84af@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®