From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] toolchain-configs.csv: re-organize for test-pkg
Date: Sun, 1 Apr 2018 16:31:18 +0200 [thread overview]
Message-ID: <20180401163118.0bd49e54@windsurf> (raw)
In-Reply-To: <20180323214815.19831-2-thomas.petazzoni@bootlin.com>
Hello,
On Fri, 23 Mar 2018 22:48:13 +0100, Thomas Petazzoni wrote:
> From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>
> This commit reorganizes the toolchain-configs.csv so that the first
> toolchains are a subset of "useful" toolchains to be tested by
> contributors to validate a package. This subset is the one that will
> be used by default by test-pkg.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> Changes since v1:
> - Add better comments to explain the two "sections" of the toolchain
> list, as suggested by Yann E. Morin.
> ---
> .../autobuild/toolchain-configs.csv | 32 ++++++++++++++++++----
> 1 file changed, 26 insertions(+), 6 deletions(-)
Series applied to master.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-04-01 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 21:48 [Buildroot] [PATCH v2 0/3] test-pkg: by default only test a subset of toolchains Thomas Petazzoni
2018-03-23 21:48 ` [Buildroot] [PATCH v2 1/3] toolchain-configs.csv: re-organize for test-pkg Thomas Petazzoni
2018-03-24 15:48 ` Yann E. MORIN
2018-04-01 14:31 ` Thomas Petazzoni [this message]
2018-03-23 21:48 ` [Buildroot] [PATCH v2 2/3] test-pkg: test a subset of toolchains by default, add -a and -n options Thomas Petazzoni
2018-03-24 2:39 ` Matthew Weber
2018-03-25 8:50 ` Yann E. MORIN
2018-03-25 19:06 ` Thomas Petazzoni
2018-03-25 19:35 ` Yann E. MORIN
2018-03-23 21:48 ` [Buildroot] [PATCH v2 3/3] docs/manual: update the documentation about test-pkg Thomas Petazzoni
2018-03-25 8:12 ` Yann E. MORIN
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=20180401163118.0bd49e54@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox