From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>,
Hari Bathini <hbathini@linux.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
stable@vger.kernel.org,
Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: [PATCH] powerpc/85xx: fix compile error without CONFIG_CRASH_DUMP
Date: Mon, 13 May 2024 23:22:01 +1000 [thread overview]
Message-ID: <171560652136.57553.2176515778576014967.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20240510080757.560159-1-hbathini@linux.ibm.com>
On Fri, 10 May 2024 13:37:57 +0530, Hari Bathini wrote:
> Since commit 5c4233cc0920 ("powerpc/kdump: Split KEXEC_CORE and
> CRASH_DUMP dependency"), crashing_cpu is not available without
> CONFIG_CRASH_DUMP. Fix compile error on 64-BIT 85xx owing to this
> change.
>
>
Applied to powerpc/next.
[1/1] powerpc/85xx: fix compile error without CONFIG_CRASH_DUMP
https://git.kernel.org/powerpc/c/7b090b6ff51b9a9f002139660672f662b95f0630
cheers
prev parent reply other threads:[~2024-05-13 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 8:07 [PATCH] powerpc/85xx: fix compile error without CONFIG_CRASH_DUMP Hari Bathini
2024-05-13 13:22 ` Michael Ellerman [this message]
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=171560652136.57553.2176515778576014967.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=chzigotzky@xenosoft.de \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).