From: Nylon Chen <nylon7@andestech.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] support/config-fragments: add Andes 32-bit (nds32) to autobuild configs
Date: Mon, 11 Feb 2019 15:45:05 +0800 [thread overview]
Message-ID: <20190211074505.GA17179@app09> (raw)
In-Reply-To: <20190204210232.0e99d517@windsurf>
On Tue, Feb 05, 2019 at 04:02:32AM +0800, Thomas Petazzoni wrote:
> Hello,
>
> On Wed, 23 Jan 2019 20:39:47 +0800
> Nylon Chen <nylon7@andestech.com> wrote:
>
> > Add a minimal nds32 autobuild configuration for the
> > internal toolchain with glibc.
>
> This autobuild configuration is using an external toolchain, so it is
> not at all testing "internal toolchain with glibc".
>
Ok, next patch I will fix commit described avoid confusing.
> Also, are you ok with analyzing the build failures that will be
> reported by our autobuilders for the nds32 architecture, investigate
> them and provide fixes ?
>
no problem, I'll help as mush as i can.
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
prev parent reply other threads:[~2019-02-11 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 12:39 [Buildroot] [PATCH v2 0/3] Add prebuilt nds32 toolchain, ae3xx board and autobuild configs support Nylon Chen
2019-01-23 12:39 ` [Buildroot] [PATCH v2 1/3] arch: add support for Andes 32-bit (nds32) architecture Nylon Chen
2019-02-04 19:57 ` Thomas Petazzoni
2019-01-23 12:39 ` [Buildroot] [PATCH v2 2/3] configs/andes_nds32_ae3xx: new defconfig Nylon Chen
2019-02-04 20:01 ` Thomas Petazzoni
2019-01-23 12:39 ` [Buildroot] [PATCH v2 3/3] support/config-fragments: add Andes 32-bit (nds32) to autobuild configs Nylon Chen
2019-02-04 20:02 ` Thomas Petazzoni
2019-02-11 7:45 ` Nylon Chen [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=20190211074505.GA17179@app09 \
--to=nylon7@andestech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox