From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Autotest mailing list <autotest@test.kernel.org>
Cc: KVM mailing list <kvm@vger.kernel.org>,
David Huff <dhuff@redhat.com>,
aeromenk@redhat.com, jasonwang@redhat.com,
Yogi <anantyog@linux.vnet.ibm.com>
Subject: KVM autotest patch queue updated
Date: Fri, 12 Jun 2009 17:06:45 -0300 [thread overview]
Message-ID: <1244837205.2822.119.camel@localhost.localdomain> (raw)
During the previous week, a significant amount of our backlog was
resolved and now our patch queue is smaller. If I did miss anything,
please let me know. Now we have 6 patches pending, as follows. Please if
you are the patch owner please consider re-working your patch or talk to
me, I can re-work it for you. Thanks!
--------------------------------------------------------------------------------
David Huff (dhuff@redhat.com)
1) unattended installs
http://kerneltrap.org/mailarchive/linux-kvm/2009/6/2/5868673
This is one of our top priorities, since we need a more robust
installation method. David is currently working on it, expect updates on
this subject soon.
Undergoing rework
2) Move kvm functional tests to a 'test' directory
http://kerneltrap.org/mailarchive/linux-kvm/2009/5/26/5812453
For the sake of organization and extensibility, this is one of the
things I would like to see done. Something that does not require us to
explicitely register tests on the kvm test class would be handy, and
having all tests under a 'tests' directory seems a Good Thing (TM) to
pursue.
Needs rework
--------------------------------------------------------------------------------
Yogi (anantyog@linux.vnet.ibm.com)
1) Support for remote migration
http://kerneltrap.org/mailarchive/linux-kvm/2009/4/30/5607344/thread
Another priority point work. Remote migration needs to be stressed out
then I ask Yogi to rework his patch, and would like to help
to get this in good shape for inclusion.
Needs rework
--------------------------------------------------------------------------------
Alexey Eromenko (aeromenk@redhat.com)
1) New test module: iperf
http://kerneltrap.org/mailarchive/linux-kvm/2009/5/31/5840973/thread
Needs rework
--------------------------------------------------------------------------------
Jason Wang (jasowang@redhat.com)
1) TAP network support in kvm-autotest
I didn't find this one on the kernel trap archives
Needs rework
--
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies
reply other threads:[~2009-06-12 20:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1244837205.2822.119.camel@localhost.localdomain \
--to=lmr@redhat.com \
--cc=aeromenk@redhat.com \
--cc=anantyog@linux.vnet.ibm.com \
--cc=autotest@test.kernel.org \
--cc=dhuff@redhat.com \
--cc=jasonwang@redhat.com \
--cc=kvm@vger.kernel.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