All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, eric.devolder@oracle.com,
	arnd@arndb.de, akpm@linux-foundation.org
Subject: + kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix.patch added to mm-nonmm-unstable branch
Date: Thu, 06 Jul 2023 09:41:50 -0700	[thread overview]
Message-ID: <20230706164151.3598CC433C8@smtp.kernel.org> (raw)


The patch titled
     Subject: kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix
has been added to the -mm mm-nonmm-unstable branch.  Its filename is
     kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix.patch

This patch will shortly appear at
     https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix.patch

This patch will later appear in the mm-nonmm-unstable branch at
    git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Before you just go and hit "reply", please:
   a) Consider who else should be cc'ed
   b) Prefer to cc a suitable mailing list as well
   c) Ideally: find the original patch on the mailing list and do a
      reply-to-all to that, adding suitable additional cc's

*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***

The -mm tree is included into linux-next via the mm-everything
branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there every 2-3 working days

------------------------------------------------------
From: "Arnd Bergmann" <arnd@arndb.de>
Subject: kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix
Date: Thu, 06 Jul 2023 14:18:36 +0200

Today's linux-next now runs into a warning on arm64 and
presumably others, with the same problem as on arm earlier:

WARNING: unmet direct dependencies detected for KEXEC
  Depends on [n]: ARCH_SUPPORTS_KEXEC [=n]
  Selected by [y]:
  - CRASH_DUMP [=y] && ARCH_SUPPORTS_CRASH_DUMP [=y]

I think the easiest way to make this reliable would be
this fixup.

Link: https://lkml.kernel.org/r/c057ba7a-3cc2-44ac-a961-fa062b909876@app.fastmail.com
Signed-off-by: "Arnd Bergmann" <arnd@arndb.de>
Cc: Eric DeVolder <eric.devolder@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 kernel/Kconfig.kexec |    1 +
 1 file changed, 1 insertion(+)

--- a/kernel/Kconfig.kexec~kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix
+++ a/kernel/Kconfig.kexec
@@ -91,6 +91,7 @@ config KEXEC_JUMP
 config CRASH_DUMP
 	bool "kernel crash dumps"
 	depends on ARCH_SUPPORTS_CRASH_DUMP
+	depends on ARCH_SUPPORTS_KEXEC
 	select CRASH_CORE
 	select KEXEC
 	help
_

Patches currently in -mm which might be from arnd@arndb.de are

kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix.patch


             reply	other threads:[~2023-07-06 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 16:41 Andrew Morton [this message]
2023-07-07 15:26 ` + kexec-consolidate-kexec-and-crash-options-into-kernel-kconfigkexec-fix.patch added to mm-nonmm-unstable branch Eric DeVolder

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=20230706164151.3598CC433C8@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=eric.devolder@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.