From: Zhaoxiangqiang <zxq_yx_007@163.com>
To: mark.cave-ayland@ilande.co.uk
Cc: qemu-devel@nongnu.org, edgar.iglesias@xilinx.com,
peter.maydell@linaro.org, pbonzini@redhat.com,
atar4qemu@gmail.com, david@gibson.dropbear.id.au,
f4bug@amsat.org
Subject: Re: [Qemu-devel] [PATCH v2 0/9] QOM'ify work for sparc
Date: Thu, 25 May 2017 07:48:12 +0000 [thread overview]
Message-ID: <9anw5k.oqi0ce.2y42k8-qmf@mail> (raw)
In-Reply-To: <e928c836-9bb0-b4bb-7d2e-a7805253a54c@ilande.co.uk>
Mark Cave-Ayland 于 2017 年 5 月 25 日 星期四 写道:
> On 20/05/17 01:28, 赵小强 wrote:
>
> > 在 2017年5月20日，08:09，Philippe Mathieu-Daudé <f4bug@amsat.org> 写道：
> >
> >>>
> >>> changes since v1:
> >>> * rebased on the latest master
> >>>
> >>> xiaoqiang zhao (9):
> >>> hw/misc: QOM'ify eccmemctl.c
> >>> hw/dma: QOM'ify sparc32_dma.c
> >>> hw/dma: QOM'ify sun4m_iommu.c
> >>> hw/misc: QOM'ify slavio_misc.c
> >>> hw/timer: QOM'ify m48txx_sysbus (pass 1)
> >>> hw/timer: QOM'ify m48txx_sysbus (pass 2)
> >>
> >> I think you can squash those 2. Any particular reason you did pass 2 in another commit?
> >
> > No，squash is ok.
>
> Okay no further comments so I'll assume everyone else is happy. Can you
> send your v3 patchset rebased onto master and I'll apply it to my queue
> right away.
>
>
> ATB,
>
> Mark.
>
>
Ok, coming soon.
prev parent reply other threads:[~2017-05-25 7:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 10:49 [Qemu-devel] [PATCH v2 0/9] QOM'ify work for sparc xiaoqiang zhao
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 1/9] hw/misc: QOM'ify eccmemctl.c xiaoqiang zhao
2017-04-29 22:28 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 2/9] hw/dma: QOM'ify sparc32_dma.c xiaoqiang zhao
2017-04-29 22:28 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 3/9] hw/dma: QOM'ify sun4m_iommu.c xiaoqiang zhao
2017-04-29 22:28 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 4/9] hw/misc: QOM'ify slavio_misc.c xiaoqiang zhao
2017-04-29 22:28 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 5/9] hw/timer: QOM'ify m48txx_sysbus (pass 1) xiaoqiang zhao
2017-05-19 23:56 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 6/9] hw/timer: QOM'ify m48txx_sysbus (pass 2) xiaoqiang zhao
2017-05-20 0:04 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 7/9] hw/timer: QOM'ify slavio_timer xiaoqiang zhao
2017-04-29 22:28 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 8/9] hw/sparc: QOM'ify sun4m.c xiaoqiang zhao
2017-04-29 22:29 ` Philippe Mathieu-Daudé
2017-04-29 10:49 ` [Qemu-devel] [PATCH v2 9/9] hw/sparc64: QOM'ify sun4u.c xiaoqiang zhao
2017-04-29 22:29 ` Philippe Mathieu-Daudé
2017-05-19 15:34 ` [Qemu-devel] [PATCH v2 0/9] QOM'ify work for sparc Mark Cave-Ayland
2017-05-20 0:09 ` Philippe Mathieu-Daudé
[not found] ` <C2B7E73D-27BA-40BE-927B-EC047A4BF5BA@163.com>
2017-05-25 7:17 ` Mark Cave-Ayland
2017-05-25 7:48 ` Zhaoxiangqiang [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=9anw5k.oqi0ce.2y42k8-qmf@mail \
--to=zxq_yx_007@163.com \
--cc=atar4qemu@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=edgar.iglesias@xilinx.com \
--cc=f4bug@amsat.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--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).