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>, Gao Xiang <xiang@kernel.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [GIT PULL] m68k fixes for v7.2
Date: Thu, 13 Aug 2026 10:01:34 +0200 [thread overview]
Message-ID: <20260813080134.1041412-1-geert@linux-m68k.org> (raw)
Hi Linus,
The following changes since commit 075b74841bd0065a3bda3440873c747938e69b68:
Linux 7.2-rc6 (2026-08-02 16:24: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-v7.2-tag2
for you to fetch changes up to 1fd495ef09eef96169a379a749c24b5e69974bb8:
m68k: Define NR_CPUS to 1 (2026-08-12 13:53:44 +0200)
----------------------------------------------------------------
m68k fixes for v7.2
- m68k: Define NR_CPUS to 1.
This fixes a long-standing but never critical before oddity on m68k,
that turned into a serious configuration issue after a recent erofs
change.
Note that this only fixes m68k; failures on architectures where NR_CPUS
depends on SMP will be fixed by a separate patch[1].
Thanks for pulling!
[1] "[PATCH] erofs: fix EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS on some UP
platforms"
https://lore.kernel.org/20260812131144.30802-1-xiang@kernel.org
----------------------------------------------------------------
Uwe Kleine-König (1):
m68k: Define NR_CPUS to 1
arch/m68k/Kconfig.cpu | 4 ++++
1 file changed, 4 insertions(+)
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:[~2026-08-13 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 8:01 Geert Uytterhoeven [this message]
2026-08-13 16:41 ` 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=20260813080134.1041412-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 \
--cc=xiang@kernel.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®