From: 赵小强 <zxq_yx_007@163.com>
To: michael@walle.cc
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/9] QOM'ify hw/intc files
Date: Thu, 2 Jun 2016 18:10:40 +0800 (CST) [thread overview]
Message-ID: <75f9853e.c79a.1551097ef33.Coremail.zxq_yx_007@163.com> (raw)
In-Reply-To: <62e4bcda877a3bc65145db6bc03cd8c7@walle.cc>
At 2016-05-09 17:24:04, michael@walle.cc wrote:
>Hi Peter,
>
>Am 2016-05-04 16:56, schrieb Peter Maydell:
>
>> SPARC, lm32, CRIS maintainers: do you want to take your patches
>> or shall I just take 1-8 through the target-arm.next tree?
>
>There are other ones (milkymist-ac97, lm32_uart, lm32_juart,
>milkymist-vgafb, milkymist-tmu2, lm32_timer, milkymist-sysctl). So
>unless you'll take these too, I'll pick them.
>
>-michael
>
michael :
Have you pick up the patch lm32_timer, milkymist-sysctl ?
next prev parent reply other threads:[~2016-06-02 10:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 10:09 [Qemu-devel] [PATCH 0/9] QOM'ify hw/intc files xiaoqiang zhao
2016-03-30 10:09 ` [Qemu-devel] [PATCH 1/9] hw/intc: QOM'ify etraxfs_pic.c xiaoqiang zhao
2016-03-30 10:09 ` [Qemu-devel] [PATCH 2/9] hw/intc: QOM'ify exynos4210_combiner.c xiaoqiang zhao
2016-03-30 10:09 ` [Qemu-devel] [PATCH 3/9] hw/intc: QOM'ify exynos4210_gic.c xiaoqiang zhao
2016-03-30 10:09 ` [Qemu-devel] [PATCH 4/9] hw/intc: QOM'ify imx_avic.c xiaoqiang zhao
2016-03-30 10:09 ` [Qemu-devel] [PATCH 5/9] hw/intc: QOM'ify lm32_pic.c xiaoqiang zhao
2016-05-09 9:01 ` michael
2016-05-04 14:56 ` [Qemu-devel] [PATCH 0/9] QOM'ify hw/intc files Peter Maydell
2016-05-04 16:40 ` Edgar E. Iglesias
2016-05-04 17:01 ` Peter Maydell
2016-05-09 9:24 ` michael
2016-05-09 9:33 ` Peter Maydell
2016-05-09 9:34 ` Peter Maydell
2016-06-02 10:10 ` 赵小强 [this message]
2016-06-02 11:01 ` Michael Walle
2016-06-02 11:47 ` xiaoqiang zhao
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=75f9853e.c79a.1551097ef33.Coremail.zxq_yx_007@163.com \
--to=zxq_yx_007@163.com \
--cc=michael@walle.cc \
--cc=peter.maydell@linaro.org \
--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).