From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, Joey Gouly <joey.gouly@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
catalin.marinas@arm.com, nd@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 0/2] Introduce macros for the offsets to reserved_pg_dir and tramp_pg_dir
Date: Wed, 3 Feb 2021 21:31:32 +0000 [thread overview]
Message-ID: <161238502581.1984248.10475428925310558534.b4-ty@kernel.org> (raw)
In-Reply-To: <20210202123658.22308-1-joey.gouly@arm.com>
On Tue, 2 Feb 2021 12:36:56 +0000, Joey Gouly wrote:
> Make the offsets to reserved_pg_dir and tramp_pg_dir less fragile by
> introducing macros that contain their offsets.
>
> Also use these macros to verify the offsets at link time.
>
> Joey Gouly (2):
> arm64: vmlinux.ld.S: add assertion for reserved_pg_dir offset
> arm64: vmlinux.ld.S: add assertion for tramp_pg_dir offset
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/2] arm64: vmlinux.ld.S: add assertion for reserved_pg_dir offset
https://git.kernel.org/arm64/c/00ef54341936
[2/2] arm64: vmlinux.ld.S: add assertion for tramp_pg_dir offset
https://git.kernel.org/arm64/c/0188a894c390
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
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:[~2021-02-03 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 12:36 [PATCH 0/2] Introduce macros for the offsets to reserved_pg_dir and tramp_pg_dir Joey Gouly
2021-02-02 12:36 ` [PATCH 1/2] arm64: vmlinux.ld.S: add assertion for reserved_pg_dir offset Joey Gouly
2021-02-02 12:36 ` [PATCH 2/2] arm64: vmlinux.ld.S: add assertion for tramp_pg_dir offset Joey Gouly
2021-02-03 12:28 ` [PATCH 0/2] Introduce macros for the offsets to reserved_pg_dir and tramp_pg_dir Mark Rutland
2021-02-03 21:31 ` 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=161238502581.1984248.10475428925310558534.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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