From: Will Deacon <will@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: bring Image header in line with latest Arm brand guidelines
Date: Wed, 1 Apr 2020 08:51:25 +0100 [thread overview]
Message-ID: <20200401075125.GA15950@willie-the-truck> (raw)
In-Reply-To: <20200401065636.1751-1-ardb@kernel.org>
Hi Ard,
On Wed, Apr 01, 2020 at 08:56:36AM +0200, Ard Biesheuvel wrote:
> The Arm brand guidelines are pretty clear when it comes to the way
> the brand name 'arm' should be displayed: it should be all lowercase,
> and there should be sufficient whitespace around it on all sides.
>
> Let's use the reserved space we have available in the Image header to
> bring it in compliance with this.
>
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> arch/arm64/include/asm/image.h | 2 +-
> arch/arm64/kernel/head.S | 7 +++----
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/include/asm/image.h b/arch/arm64/include/asm/image.h
> index c2b13213c720..a52e6eca8118 100644
> --- a/arch/arm64/include/asm/image.h
> +++ b/arch/arm64/include/asm/image.h
> @@ -3,7 +3,7 @@
> #ifndef __ASM_IMAGE_H
> #define __ASM_IMAGE_H
>
> -#define ARM64_IMAGE_MAGIC "ARM\x64"
> +#define ARM64_IMAGE_MAGIC "arm\x64"
>
> #define ARM64_IMAGE_FLAG_BE_SHIFT 0
> #define ARM64_IMAGE_FLAG_PAGE_SIZE_SHIFT (ARM64_IMAGE_FLAG_BE_SHIFT + 1)
> diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
> index 57a91032b4c2..e70d3f96dfe4 100644
> --- a/arch/arm64/kernel/head.S
> +++ b/arch/arm64/kernel/head.S
> @@ -78,10 +78,9 @@ _head:
> le64sym _kernel_offset_le // Image load offset from start of RAM, little-endian
> le64sym _kernel_size_le // Effective size of kernel image, little-endian
> le64sym _kernel_flags_le // Informative flags, little-endian
> - .quad 0 // reserved
> - .quad 0 // reserved
> - .quad 0 // reserved
> - .ascii ARM64_IMAGE_MAGIC // Magic number
> + .ascii " "
> + .ascii " " ARM64_IMAGE_MAGIC " " // Magic number
> + .ascii " "
> #ifdef CONFIG_EFI
> .long pe_header - _head // Offset to the PE header.
Thanks for the patch. As you know, we take this kind of thing very seriously
in the kernel community, which is why I'm disappointed not to see you taking
this work to its natural conclusion by introducing a new printk format
specifier for " arm ", complete with the relevant escapes to ensure the
correct shade of blue on terminal emulators that support it.
But since the bootloader communities will probably be over the moon with
this patch on its own, I see no reason to hold it up:
Acked-until-noon-by: Will Deacon <will@kernel.org>
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-01 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 6:56 [PATCH] arm64: bring Image header in line with latest Arm brand guidelines Ard Biesheuvel
2020-04-01 7:51 ` Will Deacon [this message]
2020-04-01 9:23 ` Catalin Marinas
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=20200401075125.GA15950@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--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).