From: Mark Brown <broonie@kernel.org>
To: Olof Johansson <olof@lixom.net>
Cc: Shuah Khan <shuah.kh@samsung.com>,
"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 18:11:28 +0100 [thread overview]
Message-ID: <20140813171128.GC17528@sirena.org.uk> (raw)
In-Reply-To: <CAOesGMjEMG9+uxeg_zPhhZFPi9ZdvdxapjypGLrCVtxGZh0Ejw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On Wed, Aug 13, 2014 at 09:40:34AM -0700, Olof Johansson wrote:
> Yeah, I'm in the same boat (but I don't have a public git repo with my
> scripts). They're all just big hacks to get things going, and I'm not
> so sure it makes sense to collaborate on them too much. pyboot has
> been useful to share between us, but even there it's been more work to
> share a code base than having separate copies and borrowing ideas.
> If things get turned too generic then they just become more cumbersome
> to modify and improve (or even use).
I think the reporting side is a lot more tractable than the execution
side here - there's enough going on with crunching a set of build and
boot logs into a useful report to be useful and it's a pretty common
need. The execution side is different, that's a lot more likely to be
tied into the environment especially once you start running actual
runtime tests, but there's still common elements.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-13 17:11 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 [this message]
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
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=20140813171128.GC17528@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=olof@lixom.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