From: jonathan.austin@arm.com (Jonathan Austin)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2013-discuss] [ARM ATTEND] Interested in R/M-class (!MMU), automated testing
Date: Thu, 08 Aug 2013 11:22:54 +0100 [thread overview]
Message-ID: <5203717E.203@arm.com> (raw)
In-Reply-To: <1375725497.22073.103.camel@gandalf.local.home>
On 05/08/13 18:58, Steven Rostedt wrote:
> On Mon, 2013-08-05 at 11:08 +0100, Jonathan Austin wrote:
>
>> So that seems to be at least three separate approaches. Further, I took a
>> look recently at the ktest.pl script, which looked handy but not so
>> targetted at the ARM world, where you care about testing the same thing on
>> a wide array of platforms, might want an NFS root file-system, etc.
>
> As the maintainer of ktest.pl, I would be very interested in working
> with you to make it easier to handle your requirements. This was the
> purpose of ktest.pl in the first place :-)
Thanks very much - I don't know if I'm the only one that's looked at
ktest, but hopefully some of the others that already have fuller systems
also have thoughts on this. I'll be sure to have a more thorough look at
how this might work beforehand, so that if I am at the summit I can have
some more input.
>
> I'll happily attend any of the ARM sessions that talk about testing.
>
Olof, perhaps your idea of sharing what you've recently set up could
form the core of a session? From your other email it looks like that
system is already being quite useful...
Jonny
next prev parent reply other threads:[~2013-08-08 10:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 18:23 [ARM ATTEND] Interested in R/M-class (!MMU), automated testing Jonathan Austin
2013-08-04 12:25 ` Robert Schwebel
2013-08-05 6:49 ` Olof Johansson
2013-08-05 6:49 ` Olof Johansson
2013-08-05 10:08 ` Jonathan Austin
2013-08-05 17:58 ` [Ksummit-2013-discuss] " Steven Rostedt
2013-08-08 10:22 ` Jonathan Austin [this message]
2013-08-06 23:44 ` Aaro Koskinen
2013-08-07 0:06 ` [Ksummit-2013-discuss] " Guenter Roeck
2013-08-07 0:28 ` Olof Johansson
2013-08-07 1:10 ` Fabio Estevam
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=5203717E.203@arm.com \
--to=jonathan.austin@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).