From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64/efi: efistub: apply __init annotation
Date: Thu, 15 Jan 2015 21:27:34 +0000 [thread overview]
Message-ID: <20150115212734.GD12079@codeblueprint.co.uk> (raw)
In-Reply-To: <1421094500-15659-1-git-send-email-ard.biesheuvel@linaro.org>
On Mon, 12 Jan, at 08:28:20PM, Ard Biesheuvel wrote:
> This ensures all stub component are freed when the kernel proper is
> done booting, by prefixing the names of all ELF sections that have
> the SHF_ALLOC attribute with ".init". This approach ensures that even
> implicitly emitted allocated data (like initializer values and string
> literals) are covered.
>
> At the same time, remove some __init annotations in the stub that have
> now become redundant, and add the __init annotation to handle_kernel_image
> which will now trigger a section mismatch warning without it.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> v2: fixed an issue with spurious rebuilding of object files, now setting
> $(extra-y) correctly, which also allows the .PRECIOUS: to be dropped.
>
>
> arch/arm64/kernel/efi-stub.c | 14 +++++++-------
> drivers/firmware/efi/libstub/Makefile | 14 ++++++++++++++
> drivers/firmware/efi/libstub/arm-stub.c | 8 ++++----
> drivers/firmware/efi/libstub/efi-stub-helper.c | 2 +-
> 4 files changed, 26 insertions(+), 12 deletions(-)
Applied for v3.20, thanks Ard.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2015-01-15 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 20:28 [PATCH v2] arm64/efi: efistub: apply __init annotation Ard Biesheuvel
2015-01-15 21:27 ` Matt Fleming [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=20150115212734.GD12079@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).