public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: put __boot_cpu_mode label after alignment instead of before
Date: Mon, 16 Mar 2015 10:52:07 +0000	[thread overview]
Message-ID: <20150316105206.GB15066@leverpostej> (raw)
In-Reply-To: <1426260078-20720-1-git-send-email-ard.biesheuvel@linaro.org>

On Fri, Mar 13, 2015 at 03:21:18PM +0000, Ard Biesheuvel wrote:
> Another one for the big head.S spring cleaning: the label should
> be after the .align or it may point to the padding.
> 
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

Given I managed to produce the exact same patch, this obviously looks
good to me:

Acked-by: Mark Rutland <mark.rutland@arm.com>

Mark.

> ---
>  arch/arm64/kernel/head.S | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
> index 3e300bfb0089..9c856f2aa7a5 100644
> --- a/arch/arm64/kernel/head.S
> +++ b/arch/arm64/kernel/head.S
> @@ -557,8 +557,8 @@ ENDPROC(set_cpu_boot_mode_flag)
>   * zeroing of .bss would clobber it.
>   */
>  	.pushsection	.data..cacheline_aligned
> -ENTRY(__boot_cpu_mode)
>  	.align	L1_CACHE_SHIFT
> +ENTRY(__boot_cpu_mode)
>  	.long	BOOT_CPU_MODE_EL2
>  	.long	0
>  	.popsection
> -- 
> 1.8.3.2
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 

  reply	other threads:[~2015-03-16 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 15:21 [PATCH] arm64: put __boot_cpu_mode label after alignment instead of before Ard Biesheuvel
2015-03-16 10:52 ` Mark Rutland [this message]
2015-03-16 10:58   ` Mark Rutland

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=20150316105206.GB15066@leverpostej \
    --to=mark.rutland@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