From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Greg Ungerer <gerg@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Sasha Levin <sashal@kernel.org>,
linux-m68k@lists.linux-m68k.org
Subject: [PATCH AUTOSEL 5.19 14/29] m68knommu: fix non-mmu classic 68000 legacy timer tick selection
Date: Mon, 17 Oct 2022 20:08:23 -0400 [thread overview]
Message-ID: <20221018000839.2730954-14-sashal@kernel.org> (raw)
In-Reply-To: <20221018000839.2730954-1-sashal@kernel.org>
From: Greg Ungerer <gerg@linux-m68k.org>
[ Upstream commit 18011e50c497f04a57a8e00122906f04922b30b4 ]
The family of classic 68000 parts supported when in non-mmu mode all
currently use the legacy timer support. Move the selection of that config
option, LEGACY_TIMER_TICK, into the core CPU configuration.
This fixes compilation if no specific CPU variant is selected, since
the LEGACY_TIMER_TICK option was only selected in the specific CPU
variant configurations.
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
arch/m68k/Kconfig.cpu | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu
index f3aa44156969..3fdca29422e2 100644
--- a/arch/m68k/Kconfig.cpu
+++ b/arch/m68k/Kconfig.cpu
@@ -46,6 +46,7 @@ config M68000
select GENERIC_CSUM
select CPU_NO_EFFICIENT_FFS
select HAVE_ARCH_HASH
+ select LEGACY_TIMER_TICK
help
The Freescale (was Motorola) 68000 CPU is the first generation of
the well known M68K family of processors. The CPU core as well as
@@ -97,7 +98,6 @@ config M68060
config M68328
bool
depends on !MMU
- select LEGACY_TIMER_TICK
select M68000
help
Motorola 68328 processor support.
@@ -105,7 +105,6 @@ config M68328
config M68EZ328
bool
depends on !MMU
- select LEGACY_TIMER_TICK
select M68000
help
Motorola 68EX328 processor support.
@@ -113,7 +112,6 @@ config M68EZ328
config M68VZ328
bool
depends on !MMU
- select LEGACY_TIMER_TICK
select M68000
help
Motorola 68VZ328 processor support.
--
2.35.1
next prev parent reply other threads:[~2022-10-18 0:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 0:08 [PATCH AUTOSEL 5.19 01/29] crypto: qcom-rng - Fix qcom_rng_of_match unused warning Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 02/29] crypto: ccp - Add a quirk to firmware update Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 03/29] crypto: ccp - Initialize PSP when reading psp data file failed Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 04/29] gfs2: Switch from strlcpy to strscpy Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 05/29] powerpc/hw_breakpoint: Avoid relying on caller synchronization Sasha Levin
2022-10-18 1:04 ` Marco Elver
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 06/29] cgroup: Remove data-race around cgrp_dfl_visible Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 07/29] iommu/vt-d: Handle race between registration and device probe Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 08/29] of/fdt: Don't calculate initrd size from DT if start > end Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 09/29] objtool,x86: Teach decode about LOOP* instructions Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 10/29] locking/rwsem: Disable preemption while trying for rwsem lock Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 11/29] gfs2: Check sb_bsize_shift after reading superblock Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 12/29] powerpc/64: don't refer nr_cpu_ids in asm code when it's undefined Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 13/29] m68knommu: fix non-specific 68328 choice interrupt build failure Sasha Levin
2022-10-18 0:08 ` Sasha Levin [this message]
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 15/29] kbuild: take into account DT_SCHEMA_FILES changes while checking dtbs Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 16/29] tracing/user_events: Use WRITE instead of READ for io vector import Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 17/29] tracing/user_events: Ensure user provided strings are safely formatted Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 18/29] of: Fix "dma-ranges" handling for bus controllers Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 19/29] x86/hyperv: Replace kmap() with kmap_local_page() Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 20/29] kmsan: disable instrumentation of unsupported common kernel code Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 21/29] kmsan: disable physical page merging in biovec Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 22/29] f2fs: fix wrong dirty page count when race between mmap and fallocate Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 23/29] f2fs: code clean and fix a type error Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 24/29] f2fs: fix to detect corrupted meta ino Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 25/29] 9p: trans_fd/p9_conn_cancel: drop client lock earlier Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 26/29] 9p/trans_fd: always use O_NONBLOCK read/write Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 27/29] net/9p: use a dedicated spinlock for trans_fd Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 28/29] virtio_pci: don't try to use intxif pin is zero Sasha Levin
2022-10-18 0:08 ` [PATCH AUTOSEL 5.19 29/29] cifs: replace kfree() with kfree_sensitive() for sensitive data Sasha Levin
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=20221018000839.2730954-14-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=stable@vger.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®