qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: arei.gonglei@huawei.com, qemu-devel@nongnu.org
Cc: luonengjun@huawei.com, akong@redhat.com,
	weidong.huang@huawei.com, kraxel@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/5] tests: add UHCI qtest
Date: Thu, 19 Jun 2014 14:40:34 +0200	[thread overview]
Message-ID: <53A2DA42.8040503@suse.de> (raw)
In-Reply-To: <1402992243-10224-3-git-send-email-arei.gonglei@huawei.com>

Am 17.06.2014 10:04, schrieb arei.gonglei@huawei.com:
> From: Gonglei <arei.gonglei@huawei.com>
> 
> add uhci controller hotplug/unplug qtest
> 
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> ---
>  tests/Makefile            |  3 +++
>  tests/usb-hcd-uhci-test.c | 42 ++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 45 insertions(+)
>  create mode 100644 tests/usb-hcd-uhci-test.c
> 
> diff --git a/tests/Makefile b/tests/Makefile
> index b1fbfb6..54b8af2 100644
> --- a/tests/Makefile
> +++ b/tests/Makefile
> @@ -153,6 +153,8 @@ check-qtest-i386-y += tests/ioh3420-test$(EXESUF)
>  gcov-files-i386-y += hw/pci-bridge/ioh3420.c
>  check-qtest-i386-y += tests/usb-hcd-ohci-test$(EXESUF)
>  gcov-files-i386-y += hw/usb/hcd-ohci.c
> +check-qtest-i386-y += tests/usb-hcd-uhci-test$(EXESUF)
> +gcov-files-i386-y += hw/usb/hcd-uhci.c
>  check-qtest-i386-y += tests/usb-hcd-ehci-test$(EXESUF)
>  gcov-files-i386-y += hw/usb/hcd-ehci.c

>  gcov-files-i386-y += hw/usb/hcd-uhci.c

You can drop this duplicate line then.

Again, QMP and -device testing would be nice.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-06-19 12:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17  8:03 [Qemu-devel] [PATCH 0/5] tests: add usb host adapter qtest cases arei.gonglei
2014-06-17  8:03 ` [Qemu-devel] [PATCH 1/5] tests: add OHCI qtest arei.gonglei
2014-06-19 12:34   ` Andreas Färber
2014-06-19 12:48     ` Gonglei (Arei)
2014-06-17  8:04 ` [Qemu-devel] [PATCH 2/5] tests: add UHCI qtest arei.gonglei
2014-06-19 12:40   ` Andreas Färber [this message]
2014-06-19 12:59     ` Gonglei (Arei)
2014-06-17  8:04 ` [Qemu-devel] [PATCH 3/5] tests: add xHCI qtest arei.gonglei
2014-06-19 12:37   ` Andreas Färber
2014-06-19 12:57     ` Gonglei (Arei)
2014-06-17  8:04 ` [Qemu-devel] [PATCH 4/5] usb-hcd-ehci-test: change ehci qtest more expansively arei.gonglei
2014-06-19 12:55   ` Andreas Färber
2014-06-17  8:04 ` [Qemu-devel] [PATCH 5/5] usb-hcd-ehci-test: add ehci hotplug/unplug qtest arei.gonglei
2014-06-19 10:05 ` [Qemu-devel] [PATCH 0/5] tests: add usb host adapter qtest cases Gerd Hoffmann
2014-06-19 12:18   ` Gonglei (Arei)
2014-06-19 12:24   ` Andreas Färber
2014-06-19 12:47     ` Gerd Hoffmann
2014-06-19 13:07       ` Andreas Färber
2014-06-19 13:19         ` Gonglei (Arei)
2014-06-19 13:33           ` Andreas Färber
2014-06-19 13:46             ` Gerd Hoffmann
2014-06-20  1:51               ` Gonglei (Arei)
2014-06-20  1:48             ` Gonglei (Arei)

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=53A2DA42.8040503@suse.de \
    --to=afaerber@suse.de \
    --cc=akong@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=kraxel@redhat.com \
    --cc=luonengjun@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=weidong.huang@huawei.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;
as well as URLs for NNTP newsgroup(s).