From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager via buildroot <buildroot@buildroot.org>
Cc: michal.simek@amd.com, ibai.erkiaga-elorza@amd.com,
luca.ceresoli@bootlin.com, Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH v9 05/11] toolchain/toolchain-bare-metal-buildroot: wire up newlib-bare-metal
Date: Tue, 6 Feb 2024 18:53:05 +0100 [thread overview]
Message-ID: <20240206185305.0ca3bb42@windsurf> (raw)
In-Reply-To: <20240131112223.2175855-5-neal.frager@amd.com>
On Wed, 31 Jan 2024 11:22:17 +0000
Neal Frager via buildroot <buildroot@buildroot.org> wrote:
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> toolchain/Config.in | 1 +
> toolchain/toolchain-bare-metal-buildroot/Config.in | 2 ++
> .../toolchain-bare-metal-buildroot.mk | 2 +-
> 3 files changed, 4 insertions(+), 1 deletion(-)
Applied to master, thanks.
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
next prev parent reply other threads:[~2024-02-06 17:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 11:22 [Buildroot] [PATCH v9 01/11] toolchain/toolchain-bare-metal-buildroot: new toolchain Neal Frager via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 02/11] package/binutils-bare-metal: new package Neal Frager via buildroot
2024-02-06 17:52 ` Thomas Petazzoni via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 03/11] package/gcc-bare-metal: " Neal Frager via buildroot
2024-02-06 17:52 ` Thomas Petazzoni via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 04/11] package/newlib-bare-metal: " Neal Frager via buildroot
2024-02-02 12:11 ` Frager, Neal via buildroot
2024-02-06 17:53 ` Thomas Petazzoni via buildroot
2024-02-06 17:52 ` Thomas Petazzoni via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 05/11] toolchain/toolchain-bare-metal-buildroot: wire up newlib-bare-metal Neal Frager via buildroot
2024-02-06 17:53 ` Thomas Petazzoni via buildroot [this message]
2024-01-31 11:22 ` [Buildroot] [PATCH v9 06/11] boot/zynqmp-firmware: new boot firmware Neal Frager via buildroot
2024-02-07 9:00 ` Frager, Neal via buildroot
2024-02-22 16:35 ` Frager, Neal via buildroot
2024-02-29 9:29 ` Luca Ceresoli via buildroot
2024-03-03 8:23 ` Frager, Neal via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 07/11] boot/uboot.mk: new zynqmp pmufw build option Neal Frager via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 08/11] configs/zynqmp*: build pmufw source Neal Frager via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 09/11] boot/versal-firmware: new boot firmware Neal Frager via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 10/11] configs/versal_vck190_defconfig: build plm and psmfw source Neal Frager via buildroot
2024-01-31 11:22 ` [Buildroot] [PATCH v9 11/11] package/versal-firmware: remove package Neal Frager via buildroot
2024-02-06 17:52 ` [Buildroot] [PATCH v9 01/11] toolchain/toolchain-bare-metal-buildroot: new toolchain Thomas Petazzoni via buildroot
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=20240206185305.0ca3bb42@windsurf \
--to=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.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