public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: akos.denke@arm.com, andre.przywara@arm.com,
	luca.fancellu@arm.com, maz@kernel.org
Subject: Re: [BOOT-WRAPPER 0/3] Allow use of bare-metal toolchains
Date: Fri, 2 Aug 2024 11:10:57 +0100	[thread overview]
Message-ID: <ZqywpZ8Mbv4nrqnt@J2N7QTR9R3> (raw)
In-Reply-To: <20240729143116.1804615-1-mark.rutland@arm.com>

On Mon, Jul 29, 2024 at 03:31:13PM +0100, Mark Rutland 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(-)

I've applied this series to the boot-wrapper-aarch64 master branch:

  https://git.kernel.org/pub/scm/linux/kernel/git/mark/boot-wrapper-aarch64.git/commit/?id=1fea854771f9aee405c4ae204c0e0f912318da6f

Mark.


      parent reply	other threads:[~2024-08-02 10:11 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 ` [BOOT-WRAPPER 0/3] Allow " Marc Zyngier
2024-08-02 10:10 ` Mark Rutland [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=ZqywpZ8Mbv4nrqnt@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=akos.denke@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=luca.fancellu@arm.com \
    --cc=maz@kernel.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