From: Linus Walleij <linus.walleij@linaro.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: shuah.kh@samsung.com, Rob Landley <rob@landley.net>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond
Date: Wed, 13 Aug 2014 10:35:53 +0200 [thread overview]
Message-ID: <CACRpkdZL_1Enxd2dTnaEvZkHuCfV08f74ZOqFqaRtEdyMmwtvA@mail.gmail.com> (raw)
In-Reply-To: <20140812130043.4894DC40C5C@trevor.secretlab.ca>
On Tue, Aug 12, 2014 at 3:00 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Tue, 12 Aug 2014 01:13:07 +0900, Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
>> I see, for that purpose, installing testcase may not fit.
>> BTW, how would it cover cross-build?
>
> I'm interested in this as well. I'm working on a tool that crossbuilds a
> very simple busybox rootfs and boots in QEMU for as many architectures
> as possible. I want to make it easy to sanity test all the major
> architectures. Right now it does little more than boot to a login
> prompt, but I'd like to get the kselftests into it also.
Hm that sounds like a goal similar to what Rob Landley has
described as one goal for Aboriginal Linux as well.
http://landley.net/aboriginal/about.html
If such cross builds are triggered from git pushes akin to how
Fengguang's 0-day is already working we are in a positive
flow I think.
Yours,
Linus Walleij
next prev parent reply other threads:[~2014-08-13 8:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 14:36 Shuah Khan
2014-08-07 18:24 ` Bird, Tim
2014-08-07 19:59 ` Shuah Khan
2014-08-08 2:18 ` Masami Hiramatsu
2014-08-11 14:11 ` Shuah Khan
2014-08-11 16:13 ` Masami Hiramatsu
2014-08-12 13:00 ` Grant Likely
2014-08-12 16:15 ` Guenter Roeck
2014-08-12 16:21 ` Masami Hiramatsu
2014-08-12 16:51 ` Geert Uytterhoeven
2014-08-12 17:15 ` Theodore Ts'o
2014-08-12 16:23 ` Grant Likely
2014-08-12 16:49 ` Mark Brown
2014-08-13 6:26 ` Grant Likely
2014-08-13 10:40 ` Mark Brown
2014-08-13 11:12 ` Geert Uytterhoeven
2014-08-13 12:42 ` Mark Brown
2014-08-13 13:08 ` Geert Uytterhoeven
2014-08-13 15:00 ` Kevin Hilman
2014-08-13 16:40 ` Olof Johansson
2014-08-13 17:11 ` Mark Brown
2014-08-12 17:46 ` Tim Bird
2014-08-12 18:06 ` Steven Rostedt
2014-08-12 20:52 ` Tim Bird
2014-08-14 16:35 ` Grant Likely
2014-08-12 17:30 ` Andy Lutomirski
2014-08-12 16:34 ` Shuah Khan
2014-08-13 8:35 ` Linus Walleij [this message]
2014-08-13 16:11 ` Guenter Roeck
2014-08-13 16:16 ` Andy Lutomirski
2014-08-13 16:44 ` Bird, Tim
2014-08-13 17:07 ` Grant Likely
2014-08-13 17:10 ` Andy Lutomirski
2014-08-13 17:10 ` Guenter Roeck
2014-08-18 3:10 ` Rob Landley
2014-08-18 3:08 ` Rob Landley
2014-08-18 7:16 ` Geert Uytterhoeven
2014-08-13 16:45 ` Masami Hiramatsu
2014-08-18 3:18 ` Rob Landley
2014-08-13 15:06 ` Aneesh Kumar K.V
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=CACRpkdZL_1Enxd2dTnaEvZkHuCfV08f74ZOqFqaRtEdyMmwtvA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=rob@landley.net \
--cc=shuah.kh@samsung.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