From: ebiederm@xmission.com (Eric W. Biederman)
To: Will Deacon <will@kernel.org>
Cc: james.morse@arm.com, jmorris@namei.org,
tyhicks@linux.microsoft.com, kexec@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
kernel-team@android.com
Subject: Re: [PATCH v2] kexec: move machine_kexec_post_load() to public interface
Date: Mon, 22 Feb 2021 23:16:38 -0600 [thread overview]
Message-ID: <m1im6jmki1.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <161399720788.2051103.17455817952511939013.b4-ty@kernel.org> (Will Deacon's message of "Mon, 22 Feb 2021 14:29:01 +0000")
Will Deacon <will@kernel.org> writes:
> On Fri, 19 Feb 2021 14:51:42 -0500, Pavel Tatashin wrote:
>> machine_kexec_post_load() is called after kexec load is finished. It must
>> declared in public header not in kexec_internal.h
>>
>> Fixes the following compiler warning:
>>
>> arch/arm64/kernel/machine_kexec.c:62:5: warning: no previous prototype for
>> function 'machine_kexec_post_load' [-Wmissing-prototypes]
>> int machine_kexec_post_load(struct kimage *kimage)
>
> Applied to arm64 (for-next/fixes), thanks!
>
> [1/1] kexec: move machine_kexec_post_load() to public interface
> https://git.kernel.org/arm64/c/2596b6ae412b
As you have already applied this it seems a bit late,
but I will mention that change could legitimately have the following
tag.
Fixes: de68e4daea90 ("kexec: add machine_kexec_post_load()")
So far arm64 is the only implementation of that hook.
Eric
next prev parent reply other threads:[~2021-02-23 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 19:51 Pavel Tatashin
2021-02-22 14:29 ` Will Deacon
2021-02-23 5:16 ` Eric W. Biederman [this message]
2021-02-23 9:45 ` Will Deacon
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=m1im6jmki1.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jmorris@namei.org \
--cc=kernel-team@android.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=tyhicks@linux.microsoft.com \
--cc=will@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
all inboxes | Powered by JetHome®