ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Andy Lutomirski <luto@amacapital.net>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Hallway/unconference track: easy QEMU-based testing tools
Date: Tue, 19 Aug 2014 07:51:40 -0700	[thread overview]
Message-ID: <20140819145140.GA18536@roeck-us.net> (raw)
In-Reply-To: <CALCETrUN8w1v45nNaJkQ-n6jASqNA+sJ+vk+R1VWfToPKqD00g@mail.gmail.com>

On Tue, Aug 19, 2014 at 07:37:27AM -0700, Andy Lutomirski wrote:
> I have a tool (virtme) for easy kernel testing, and I think that several of
> you have similar or complementary things.  I think it would we worthwhile
> to spend ten minutes or so to compare notes and use cases.

We have a session scheduled for kselftest, which as I understand will cover qemu
based testing as well. 11am in Ontario conference room.

Guenter

  reply	other threads:[~2014-08-19 14:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 14:37 Andy Lutomirski
2014-08-19 14:51 ` Guenter Roeck [this message]
2014-08-19 15:04   ` Andy Lutomirski

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=20140819145140.GA18536@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=luto@amacapital.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