From: Mark Rutland <mark.rutland@arm.com>
To: Luca Fancellu <luca.fancellu@arm.com>
Cc: andre.przywara@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [boot-wrapper v3 1/4] Introduce --with-bw-arch for boot-wrapper compile arch
Date: Fri, 11 Oct 2024 11:50:08 +0100 [thread overview]
Message-ID: <ZwkC4ADX7hM8F6QC@J2N7QTR9R3> (raw)
In-Reply-To: <20240731141103.2559706-2-luca.fancellu@arm.com>
On Wed, Jul 31, 2024 at 03:11:00PM +0100, Luca Fancellu wrote:
> Introduce a new autoconf parameter --with-bw-arch that takes
> 'aarch64-a' and 'aarch32-a' as compile architecture, the former
> is selected by default when the parameter is not passed.
>
> This new parameter superseed --enable-aarch32-bw, its functionality
> is now implemented by --with-bw-arch=aarch32-a.
>
> Signed-off-by: Luca Fancellu <luca.fancellu@arm.com>
> ---
> Changes from v2:
> - Major rework, reason in the cover letter.
> ---
> configure.ac | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index ce41daebc378..bba42fa1dba8 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -9,9 +9,18 @@ AC_INIT([boot-wrapper], [v0.2])
>
> AM_INIT_AUTOMAKE([foreign])
>
> -AC_ARG_ENABLE([aarch32-bw],
> - AS_HELP_STRING([--enable-aarch32-bw], [build a 32-bit boot-wrapper]),
> - [BOOTWRAPPER_ES=32], [BOOTWRAPPER_ES=64])
> +# Allow a user to pass --with-bw-arch={aarch64-a,aarch32-a}
> +AC_ARG_WITH([bw-arch],
> + AS_HELP_STRING([--with-bw-arch], [aarch64-a selects AArch64-A (default), aarch32-a selects AArch32-A]),
Could we we please make the help text:
specify boot-wrapper architecture: aarch64-a (default) or aarch32-a
That way ist says what the option does, and it avoids the repeition.
With that change I think this looks good to go.
Mark.
> + [case "${withval}" in
> + no|yes|aarch64-a) USE_ARCH=aarch64-a ;;
> + aarch32-a) USE_ARCH=aarch32-a ;;
> + *) AC_MSG_ERROR([Bad value "${withval}" for --with-bw-arch. Use "aarch64-a" or "aarch32-a"]) ;;
> + esac])
> +
> +AS_IF([test "x$USE_ARCH" = "xaarch32-a"],
> + [BOOTWRAPPER_ES=32], [BOOTWRAPPER_ES=64]
> +)
> AM_CONDITIONAL([BOOTWRAPPER_32], [test "x$BOOTWRAPPER_ES" = "x32"])
>
> AC_ARG_ENABLE([aarch32-kernel],
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-10-11 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 14:10 [boot-wrapper v3 0/4] Add Armv8-R AArch64 support Luca Fancellu
2024-07-31 14:11 ` [boot-wrapper v3 1/4] Introduce --with-bw-arch for boot-wrapper compile arch Luca Fancellu
2024-10-11 10:50 ` Mark Rutland [this message]
2024-07-31 14:11 ` [boot-wrapper v3 2/4] aarch64: Enable Armv8-R EL2 boot Luca Fancellu
2024-10-11 10:52 ` Mark Rutland
2024-10-14 18:25 ` Luca Fancellu
2024-10-17 9:30 ` Mark Rutland
2024-07-31 14:11 ` [boot-wrapper v3 3/4] aarch64: Implement PSCI for Armv8-R Luca Fancellu
2024-10-11 10:55 ` Mark Rutland
2024-07-31 14:11 ` [boot-wrapper v3 4/4] aarch64: Start Xen on Armv8-R at EL2 Luca Fancellu
2024-10-11 10:56 ` 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=ZwkC4ADX7hM8F6QC@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=andre.przywara@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=luca.fancellu@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