From: Marc Zyngier <maz@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, akos.denke@arm.com,
andre.przywara@arm.com, luca.fancellu@arm.com
Subject: Re: [BOOT-WRAPPER 0/3] Allow use of bare-metal toolchains
Date: Fri, 02 Aug 2024 10:21:29 +0100 [thread overview]
Message-ID: <86ikwj1dra.wl-maz@kernel.org> (raw)
In-Reply-To: <20240729143116.1804615-1-mark.rutland@arm.com>
On Mon, 29 Jul 2024 15:31:13 +0100,
Mark Rutland <mark.rutland@arm.com> wrote:
>
> Since the boot-wrapper build system was migrated to autoconf it hasn't
> been possible to build the boot-wrapper with a bare-metal toolchain,
> since the configure sscript checks for a hosted toolchain.
>
> These patches make it possible to build the boot-wrapper with a
> bare-metal toolchain.
>
> Mark.
>
> Mark Rutland (3):
> Makefile: rework test-dtc-option
> Makefile: suppress RWX segment warnings
> configure: allow the use of bare-metal toolchains
>
> Makefile.am | 20 +++++++++++++++-----
> configure.ac | 3 +++
> 2 files changed, 18 insertions(+), 5 deletions(-)
All looks reasonable to me.
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-08-02 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 14:31 [BOOT-WRAPPER 0/3] Allow use of bare-metal toolchains Mark Rutland
2024-07-29 14:31 ` [BOOT-WRAPPER 1/3] Makefile: rework test-dtc-option Mark Rutland
2024-07-29 14:31 ` [BOOT-WRAPPER 2/3] Makefile: suppress RWX segment warnings Mark Rutland
2024-07-29 14:31 ` [BOOT-WRAPPER 3/3] configure: allow the use of bare-metal toolchains Mark Rutland
2024-08-02 9:21 ` Marc Zyngier [this message]
2024-08-02 10:10 ` [BOOT-WRAPPER 0/3] Allow " 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=86ikwj1dra.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=akos.denke@arm.com \
--cc=andre.przywara@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=luca.fancellu@arm.com \
--cc=mark.rutland@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