From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 3/3] support/config-fragments: add RISC-V 32-bit to autobuild configs
Date: Thu, 10 Jan 2019 21:32:15 +0100 [thread overview]
Message-ID: <20190110213215.17b8de76@windsurf> (raw)
In-Reply-To: <20181021191203.2148-3-mark.corbin@embecosm.com>
Hello,
On Sun, 21 Oct 2018 20:12:03 +0100, Mark Corbin wrote:
> Add a minimal RISC-V 32-bit autobuild configuration for the
> internal toolchain with glibc.
>
> Signed-off-by: Mark Corbin <mark.corbin@embecosm.com>
>
> ---
> Changes v3 -> v4:
> - set new variable BR2_RISCV_32 in br-riscv32-internal-glibc.config
> ---
> .../autobuild/br-riscv32-internal-glibc.config | 3 +++
> support/config-fragments/autobuild/toolchain-configs.csv | 1 +
> 2 files changed, 4 insertions(+)
> create mode 100644 support/config-fragments/autobuild/br-riscv32-internal-glibc.config
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-10 20:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 19:12 [Buildroot] [PATCH v4 1/3] arch: add support for RISC-V 32-bit (riscv32) architecture Mark Corbin
2018-10-21 19:12 ` [Buildroot] [PATCH v4 2/3] configs/qemu: add qemu_riscv32_virt_defconfig Mark Corbin
2018-11-02 3:09 ` Matthew Weber
2019-01-10 20:32 ` Thomas Petazzoni
2018-10-21 19:12 ` [Buildroot] [PATCH v4 3/3] support/config-fragments: add RISC-V 32-bit to autobuild configs Mark Corbin
2018-11-02 3:09 ` Matthew Weber
2019-01-10 20:32 ` Thomas Petazzoni [this message]
2018-11-02 3:08 ` [Buildroot] [PATCH v4 1/3] arch: add support for RISC-V 32-bit (riscv32) architecture Matthew Weber
2019-01-06 13:18 ` Thomas Petazzoni
2019-01-07 14:36 ` Mark Corbin
2019-01-07 15:21 ` Thomas Petazzoni
2019-01-14 20:44 ` Thomas Petazzoni
2019-01-15 10:19 ` Mark Corbin
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=20190110213215.17b8de76@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.