From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Subject: Re: powerpc: Fix build of 64 bit little endian with CONFIG_KEXEC=n
Date: Thu, 8 Sep 2016 19:47:55 +1000 (AEST) [thread overview]
Message-ID: <3sVFrC3mwzz9s9N@ozlabs.org> (raw)
In-Reply-To: <1471993059-19239-1-git-send-email-bauerman@linux.vnet.ibm.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Tue, 2016-23-08 at 22:57:39 UTC, Thiago Jung Bauermann wrote:
> On ppc64le, builds with CONFIG_KEXEC=n fail with:
>
> arch/powerpc/platforms/pseries/setup.c: In function ‘pseries_big_endian_exceptions’:
> arch/powerpc/platforms/pseries/setup.c:403:13: error: implicit
> declaration of function ‘kdump_in_progress’ [-Werror=implicit-function-declaration]
> if (rc && !kdump_in_progress())
>
> This is because pseries/setup.c includes <linux/kexec.h>, but
> kdump_in_progress is defined in <asm/kexec.h>. This is a problem because
> the former only includes the latter if CONFIG_KEXEC_CORE=y.
>
> Fix by including <asm/kexec.h> directly, as is done in powernv/setup.c.
>
> Fixes: d3cbff1b5a90 ("powerpc: Put exception configuration in a common place")
> Signed-off-by: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/d81d8258218228d3137055afe8
cheers
prev parent reply other threads:[~2016-09-08 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 22:57 [PATCH] powerpc: Fix build of 64 bit little endian with CONFIG_KEXEC=n Thiago Jung Bauermann
2016-09-08 9:47 ` 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=3sVFrC3mwzz9s9N@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=bauerman@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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 NNTP newsgroup(s).