qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: xiaoqiang zhao <zxq_yx_007@163.com>
To: qemu-devel@nongnu.org
Cc: i.mitsyanko@gmail.com, peter.maydell@linaro.org,
	qemu-arm@nongnu.org, zhaoshenglong@huawei.com
Subject: Re: [Qemu-devel] [PATCH 00/12] some ARM platform QOM'ify work (update)
Date: Mon, 13 Jun 2016 18:51:56 +0800	[thread overview]
Message-ID: <575E904C.3090702@163.com> (raw)
In-Reply-To: <1465813931-20534-1-git-send-email-zxq_yx_007@163.com>



在 2016年06月13日 18:31, xiaoqiang zhao 写道:
> This patch series QOM'ify ARM platform related devices.
> Where we drop the sysbus init function if possible and use
> instance_init and DeviceClass::realize function.
>
> xiaoqiang zhao (12):
>    hw/i2c: QOM'ify bitbang_i2c.c
>    hw/i2c: QOM'ify exynos4210_i2c.c
>    hw/i2c: QOM'ify omap_i2c.c
>    hw/i2c: QOM'ify versatile_i2c.c
>    hw/gpio: QOM'ify omap_gpio.c
>    hw/gpio: QOM'ify pl061.c
>    hw/gpio: QOM'ify zaurus.c
>    hw/misc: QOM'ify arm_l2x0.c
>    hw/misc: QOM'ify exynos4210_pmu.c
>    hw/misc: QOM'ify mst_fpga.c
>    hw/dma: QOM'ify pxa2xx_dma.c
>    hw/sd: QOM'ify pl181.c
>
>   hw/dma/pxa2xx_dma.c      | 38 +++++++++++++++++-------------
>   hw/gpio/omap_gpio.c      | 61 ++++++++++++++++++++++++------------------------
>   hw/gpio/pl061.c          | 24 +++++++------------
>   hw/gpio/zaurus.c         | 14 +++++------
>   hw/i2c/bitbang_i2c.c     | 14 +++++------
>   hw/i2c/exynos4210_i2c.c  | 13 +++++------
>   hw/i2c/omap_i2c.c        | 44 ++++++++++++++++++++--------------
>   hw/i2c/versatile_i2c.c   | 19 +++++----------
>   hw/misc/arm_l2x0.c       | 11 ++++-----
>   hw/misc/exynos4210_pmu.c | 11 ++++-----
>   hw/misc/mst_fpga.c       | 13 +++++------
>   hw/sd/pl181.c            | 26 +++++++++++++--------
>   12 files changed, 143 insertions(+), 145 deletions(-)
>
Sorry for the inconvenience. Please forget this thread.
I will resend soon.

      parent reply	other threads:[~2016-06-13 10:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 10:31 [Qemu-devel] [PATCH 00/12] some ARM platform QOM'ify work (update) xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 01/12] hw/i2c: QOM'ify bitbang_i2c.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 02/12] hw/i2c: QOM'ify exynos4210_i2c.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 03/12] hw/i2c: QOM'ify omap_i2c.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 04/12] hw/i2c: QOM'ify versatile_i2c.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 05/12] hw/gpio: QOM'ify omap_gpio.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 06/12] hw/gpio: QOM'ify pl061.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 07/12] hw/gpio: QOM'ify zaurus.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 08/12] hw/misc: QOM'ify arm_l2x0.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 09/12] hw/misc: QOM'ify exynos4210_pmu.c xiaoqiang zhao
2016-06-13 10:32 ` [Qemu-devel] [PATCH 10/12] hw/misc: QOM'ify mst_fpga.c xiaoqiang zhao
2016-06-13 10:51 ` xiaoqiang zhao [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=575E904C.3090702@163.com \
    --to=zxq_yx_007@163.com \
    --cc=i.mitsyanko@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zhaoshenglong@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).