From: Amos Kong <akong@redhat.com>
To: lmr@redhat.com
Cc: autotest@test.kernel.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] [Autotest PATCH 00/14] Patchset of network related subtests
Date: Tue, 20 Jul 2010 08:03:02 +0800 [thread overview]
Message-ID: <20100720000217.8213.67968.stgit@z> (raw)
The following series contain 11 network related subtests, welcome to give me
some suggestions about correctness, design, enhancement.
Thank you so much!
---
Amos Kong (14):
KVM-test: Add a new macaddress pool algorithm
KVM Test: Add a function get_interface_name() to kvm_net_utils.py
KVM Test: Add a common ping module for network related tests
KVM-test: Add a new subtest ping
KVM-test: Add a subtest jumbo
KVM-test: Add basic file transfer test
KVM-test: Add a subtest of load/unload nic driver
KVM-test: Add a subtest of nic promisc
KVM-test: Add a subtest of multicast
KVM-test: Add a subtest of pxe
KVM-test: Add a subtest of changing mac address
KVM-test: Add a subtest of netperf
KVM-test: Improve vlan subtest
KVM-test: Add subtest of testing offload by ethtool
0 files changed, 0 insertions(+), 0 deletions(-)
--
Amos Kong
reply other threads:[~2010-07-20 0:03 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=20100720000217.8213.67968.stgit@z \
--to=akong@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=qemu-devel@nongnu.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).