From: Peter Maydell <peter.maydell@linaro.org>
To: 赵小强 <zxq_yx_007@163.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Igor Mitsyanko <i.mitsyanko@gmail.com>,
Fabien Chouteau <chouteau@adacore.com>,
Peter Chubb <peter.chubb@nicta.com.au>,
Michael Walle <michael@walle.cc>,
Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v1 0/9] QOM'ify hw/intc files
Date: Thu, 5 May 2016 11:46:55 +0100 [thread overview]
Message-ID: <CAFEAcA-7djB6wwa1Y3AJv9n2SWmRcQx_ZtN+FUcwhuEso7oBKg@mail.gmail.com> (raw)
In-Reply-To: <6b415ab4.11429.15480824d26.Coremail.zxq_yx_007@163.com>
On 5 May 2016 at 11:41, 赵小强 <zxq_yx_007@163.com> wrote:
> At 2016-05-05 18:39:52, "Peter Maydell" <peter.maydell@linaro.org> wrote:
>>On 5 May 2016 at 11:28, xiaoqiang zhao <zxq_yx_007@163.com> wrote:
>>> This patch set QOM'ify files under hw/intc directory. See each commit
>>> message for details.
>>>
>>> Changes in v1:
>>> use error_setg instead of error_report in realize function
>>
>>How can you have changes in a v1? Was this supposed to be v2?
> Yes, should be v2 here. Sorry ! need a resend ?
No. Is only the last patch changed from the previous set ?
thanks
-- PMM
next prev parent reply other threads:[~2016-05-05 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 10:28 [Qemu-devel] [PATCH v1 0/9] QOM'ify hw/intc files xiaoqiang zhao
2016-05-05 10:28 ` [Qemu-devel] [PATCH v1 1/9] hw/intc: QOM'ify etraxfs_pic.c xiaoqiang zhao
2016-05-05 14:24 ` Edgar E. Iglesias
2016-05-05 10:28 ` [Qemu-devel] [PATCH v1 2/9] hw/intc: QOM'ify exynos4210_combiner.c xiaoqiang zhao
2016-05-05 10:28 ` [Qemu-devel] [PATCH v1 3/9] hw/intc: QOM'ify exynos4210_gic.c xiaoqiang zhao
2016-05-05 10:28 ` [Qemu-devel] [PATCH v1 4/9] hw/intc: QOM'ify imx_avic.c xiaoqiang zhao
2016-05-05 10:28 ` [Qemu-devel] [PATCH v1 5/9] hw/intc: QOM'ify lm32_pic.c xiaoqiang zhao
2016-05-05 10:39 ` [Qemu-devel] [PATCH v1 0/9] QOM'ify hw/intc files Peter Maydell
2016-05-05 10:41 ` 赵小强
2016-05-05 10:46 ` Peter Maydell [this message]
2016-05-05 10:48 ` 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=CAFEAcA-7djB6wwa1Y3AJv9n2SWmRcQx_ZtN+FUcwhuEso7oBKg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=blauwirbel@gmail.com \
--cc=chouteau@adacore.com \
--cc=edgar.iglesias@gmail.com \
--cc=i.mitsyanko@gmail.com \
--cc=michael@walle.cc \
--cc=peter.chubb@nicta.com.au \
--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).