qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: xiaoqiang zhao <zxq_yx_007@163.com>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] tusb6010: move from hw/timer to hw/usb
Date: Mon, 22 Feb 2016 09:38:21 +0100	[thread overview]
Message-ID: <1456130301.29896.29.camel@redhat.com> (raw)
In-Reply-To: <1455883404-10976-1-git-send-email-peter.maydell@linaro.org>

On Fr, 2016-02-19 at 12:03 +0000, Peter Maydell wrote:
> The TUSB6010 is a USB controller (as the name suggests). Move it from
> hw/timer (where it was accidentally filed in 2013 when we moved
> everything out of hw/) to hw/usb.

Added to usb queue.

thanks,
  Gerd

      reply	other threads:[~2016-02-22  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 12:03 [Qemu-devel] [PATCH] tusb6010: move from hw/timer to hw/usb Peter Maydell
2016-02-22  8:38 ` Gerd Hoffmann [this message]

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=1456130301.29896.29.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zxq_yx_007@163.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).