From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] Config.in.legacy: fix removed bootlin riscv64 toolchains
Date: Wed, 5 Jan 2022 08:54:40 +0100 [thread overview]
Message-ID: <20220105085440.6581a038@windsurf> (raw)
In-Reply-To: <20220104171128.956397-1-arnout@mind.be>
Hello Arnout,
On Tue, 4 Jan 2022 18:11:28 +0100
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> wrote:
> commit b3c66481e1f1503fcbf193d0c780271e880ad500 replaced RISC-V LP64
> bootlin toolchains by RISC-V LP64D. However, Config.in.legacy was added
> for BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_GLIBC_STABLE, which never
> existed (the stable version was only added after the switch to LP64D).
> Conversely, BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_MUSL_BLEEDING_EDGE,
> which was removed, was not mentioned in Config.in.legacy.
>
> Correct the symbol name and its comment in Config.in.legacy.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Config.in.legacy | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Too late, but:
Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Thanks for fixing this!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-05 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 17:11 [Buildroot] [PATCH] Config.in.legacy: fix removed bootlin riscv64 toolchains Arnout Vandecappelle (Essensium/Mind)
2022-01-04 22:14 ` Yann E. MORIN
2022-01-05 7:54 ` Thomas Petazzoni [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=20220105085440.6581a038@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.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