From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Guenter Roeck <linux@roeck-us•net>,
Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linux-kernel@vger•kernel.org, Nicholas Piggin <npiggin@gmail•com>,
Paul Mackerras <paulus@samba•org>,
linuxppc-dev@lists•ozlabs.org, Guenter Roeck <linux@roeck-us•net>
Subject: Re: [1/2] powerpc/kdump: Add missing optional dummy functions
Date: Wed, 14 Feb 2018 16:43:47 +1100 (AEDT) [thread overview]
Message-ID: <3zh7cg63zDz9t67@ozlabs.org> (raw)
In-Reply-To: <1518474848-3158-1-git-send-email-linux@roeck-us.net>
On Mon, 2018-02-12 at 22:34:07 UTC, Guenter Roeck wrote:
> If KEXEC_CORE is not enabled, PowerNV builds fail as follows.
>
> arch/powerpc/platforms/powernv/smp.c: In function 'pnv_smp_cpu_kill_self':
> arch/powerpc/platforms/powernv/smp.c:236:4: error:
> implicit declaration of function 'crash_ipi_callback'
>
> Add dummy function calls, similar to kdump_in_progress(), to solve the
> problem.
>
> Fixes: 4145f358644b ("powernv/kdump: Fix cases where the kdump kernel ...")
> Cc: Balbir Singh <bsingharora@gmail•com>
> Cc: Michael Ellerman <mpe@ellerman•id.au>
> Cc: Nicholas Piggin <npiggin@gmail•com>
> Signed-off-by: Guenter Roeck <linux@roeck-us•net>
> Acked-by: Balbir Singh <bsingharora@gmail•com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/910961754572a2f4c83ad7e610d180
cheers
prev parent reply other threads:[~2018-02-14 5:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 22:34 [PATCH 1/2] powerpc/kdump: Add missing optional dummy functions Guenter Roeck
2018-02-12 22:34 ` [PATCH 2/2] powerpc/pseries: Declare optional dummy function for find_and_online_cpu_nid Guenter Roeck
2018-02-13 19:49 ` Tyrel Datwyler
2018-02-14 5:43 ` [2/2] " Michael Ellerman
2018-02-12 23:01 ` [PATCH 1/2] powerpc/kdump: Add missing optional dummy functions Balbir Singh
2018-02-12 23:25 ` Guenter Roeck
2018-02-14 2:32 ` Balbir Singh
2018-02-13 11:49 ` Michael Ellerman
2018-02-14 5:43 ` 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=3zh7cg63zDz9t67@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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