From: Will Deacon <will@kernel.org>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
ardb@kernel.org, catalin.marinas@arm.com
Subject: Re: [PATCH v1] arm64: mm: fix resume for 52-bit enabled builds
Date: Fri, 9 Sep 2022 11:23:03 +0100 [thread overview]
Message-ID: <20220909102302.GA32632@willie-the-truck> (raw)
In-Reply-To: <20220909083811.33818-1-joey.gouly@arm.com>
Hi Joey,
On Fri, Sep 09, 2022 at 09:38:11AM +0100, Joey Gouly wrote:
> __cpu_setup() was changed to take the actual number of VA bits in x0,
> however the resume path was not updated at the same time.
>
> Load `vabits_actual` in the resume path, to ensure that the correct
> number of VA bits is used.
>
> This fixes booting v6.0-rc kernels on my Juno.
>
> Fixes: 0aaa68532e9d ("arm64: mm: fix booting with 52-bit address space")
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ard Biesheuvel <ardb@kernel.org>
I can't apply this without your SoB line.
I think you made this mistake in the past, so please could you try to
fix your setup? There's probably a better way to do this, but I up having:
[commit]
template = ~/linux-commit.template
in my .gitconfig, and then I put the SoB line in the template so it's
always there when I start writing the commit message.
Cheers,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-09 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 8:38 [PATCH v1] arm64: mm: fix resume for 52-bit enabled builds Joey Gouly
2022-09-09 9:11 ` Ard Biesheuvel
2022-09-09 10:23 ` Will Deacon [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=20220909102302.GA32632@willie-the-truck \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nd@arm.com \
/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