public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: linux-m68k@vger.kernel.org
Cc: Greg Ungerer <gerg@linux-m68k.org>
Subject: [PATCH 3/3] m68k: allow kexec on all MMU enabled CPUs
Date: Fri, 26 Aug 2022 14:03:02 +1000	[thread overview]
Message-ID: <20220826040302.3455339-3-gerg@linux-m68k.org> (raw)
In-Reply-To: <20220826040302.3455339-1-gerg@linux-m68k.org>

The configuration setting for 68k kexec support limits it to only
the classic 68k CPU types (so no ColdFire). However the underlying
support can handle any 68k CPU that is MMU enabled - and that includes
ColdFire. (Of course that support is only as good as mentioned in
the current configuration help).

None of the no-MMU CPU types (classic or ColdFire) have support for
kexec yet, so the configuration as it stands is not quite right, and
it will fail to compile on them.

Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
---
 arch/m68k/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
index b06faf6c0b27..fa6e69ec0b38 100644
--- a/arch/m68k/Kconfig
+++ b/arch/m68k/Kconfig
@@ -87,7 +87,7 @@ config MMU_SUN3
 
 config KEXEC
 	bool "kexec system call"
-	depends on M68KCLASSIC
+	depends on MMU
 	select KEXEC_CORE
 	help
 	  kexec is a system call that implements the ability to shutdown your
-- 
2.25.1


  parent reply	other threads:[~2022-08-26  4:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  4:03 [PATCH 1/3] m68knommu: fix non-specific 68328 choice interrupt build failure Greg Ungerer
2022-08-26  4:03 ` [PATCH 2/3] m68knommu: fix non-mmu classic 68000 legacy timer tick selection Greg Ungerer
2022-08-26  7:39   ` Geert Uytterhoeven
2022-08-26  4:03 ` Greg Ungerer [this message]
2022-08-26  7:44   ` [PATCH 3/3] m68k: allow kexec on all MMU enabled CPUs Geert Uytterhoeven
2022-08-30  7:23     ` Greg Ungerer
2022-08-30  7:36       ` Geert Uytterhoeven
2022-08-26  7:38 ` [PATCH 1/3] m68knommu: fix non-specific 68328 choice interrupt build failure Geert Uytterhoeven

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=20220826040302.3455339-3-gerg@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=linux-m68k@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