From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Grant Likely <grant.likely@secretlab.ca>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Fwd: Rough notes from testing unconference
Date: Sun, 24 Aug 2014 11:37:00 -0700 [thread overview]
Message-ID: <53FA30CC.9020404@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdUJhghbOS0JiMidxLjNXe-Gofheb0A1pB_8kJemtak-6w@mail.gmail.com>
On 08/24/2014 11:15 AM, Geert Uytterhoeven wrote:
> On Sun, Aug 24, 2014 at 7:12 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>> Cross building the kernel isn't the problem. That's easy. Getting a
>> rootfs and the tests into the rootfs can be hard, depending on the
>> platform (a problem for some embedded targets).
>
> In the past, I have used OpenWRT to build the rootfs for the test
> target.
>
I very much prefer Grant's direct method - it ensures that the available
test code is automatically integrated into the root file system, and that
there are no architecture / target dependencies.
For my part I have used various means to create root file systems for my
own tests, depending on the architecture. I see it as significant improvement
to have it all together in a single place, in our control, and to have it
as simple as possible.
Guenter
next prev parent reply other threads:[~2014-08-24 18:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140819163621.GA15109@linux.vnet.ibm.com>
2014-08-22 14:19 ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Grant Likely
2014-08-22 17:59 ` Shuah Khan
2014-08-22 18:08 ` Amit Kucheria
2014-08-28 21:54 ` Shuah Khan
2014-08-23 13:35 ` Bird, Tim
2014-08-23 21:12 ` Grant Likely
2014-08-30 1:09 ` [Ksummit-discuss] [kselftest] kselftest wiki (was RE: Fwd: Rough notes from testing unconference) Bird, Tim
2014-08-30 1:09 ` [kselftest] kselftest wiki (was RE: [Ksummit-discuss] " Bird, Tim
2014-08-30 1:09 ` Bird, Tim
2014-08-30 2:55 ` [Ksummit-discuss] [kselftest] kselftest wiki (was " Shuah Khan
2014-08-30 2:55 ` [kselftest] kselftest wiki (was RE: [Ksummit-discuss] " Shuah Khan
2014-08-30 2:55 ` Shuah Khan
2014-08-30 5:15 ` [Ksummit-discuss] [kselftest] kselftest wiki (was " Konstantin Ryabitsev
2014-08-23 8:12 ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Fengguang Wu
2014-08-24 17:12 ` Grant Likely
2014-08-24 18:14 ` Guenter Roeck
2014-08-25 9:23 ` Grant Likely
2014-08-25 10:43 ` Guenter Roeck
2014-08-24 18:15 ` Geert Uytterhoeven
2014-08-24 18:37 ` Guenter Roeck [this message]
2014-08-24 18:47 ` Olof Johansson
2014-08-24 19:14 ` Jason Cooper
2014-08-24 19:16 ` Jason Cooper
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=53FA30CC.9020404@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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.