From: Will Deacon <will@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Ard Biesheuvel <ardb@kernel.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] arm64: remove special treatment for the link order of head.o
Date: Mon, 7 Nov 2022 19:08:36 +0000 [thread overview]
Message-ID: <166783716442.32724.935158280857906499.b4-ty@kernel.org> (raw)
In-Reply-To: <20221012233500.156764-1-masahiroy@kernel.org>
On Thu, 13 Oct 2022 08:35:00 +0900, Masahiro Yamada wrote:
> In the previous discussion (see the Link tag), Ard pointed out that
> arm/arm64/kernel/head.o does not need any special treatment - the only
> piece that must appear right at the start of the binary image is the
> image header which is emitted into .head.text.
>
> The linker script does the right thing to do. The build system does
> not need to manipulate the link order of head.o.
>
> [...]
Applied to arm64 (for-next/kbuild), thanks!
[1/1] arm64: remove special treatment for the link order of head.o
https://git.kernel.org/arm64/c/994b7ac1697b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2022-11-07 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 23:35 Masahiro Yamada
2022-10-13 17:07 ` Nicolas Schier
2022-11-07 19:08 ` Will Deacon [this message]
2023-03-21 22:26 ` Aurelien Jarno
2023-03-22 14:51 ` Ard Biesheuvel
2023-03-23 21:12 ` Aurelien Jarno
2023-03-24 11:33 ` Ard Biesheuvel
2023-03-24 23:33 ` Alexei Starovoitov
2023-03-28 4:05 ` Andrii Nakryiko
2023-03-25 6:05 ` Masahiro Yamada
2023-03-25 11:42 ` Masahiro Yamada
2023-03-28 10:33 ` Eduard Zingerman
2023-03-28 19:52 ` Arnaldo Carvalho de Melo
2023-04-29 7:29 ` Aurelien Jarno
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=166783716442.32724.935158280857906499.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nicolas@fjasle.eu \
/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
all inboxes | Powered by JetHome®