From: Michael Walle <michael@walle.cc>
To: xiaoqiang zhao <zxq_yx_007@163.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
peter.maydell@linaro.org, edgar.iglesias@gmail.com,
agraf@suse.de, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 0/5] QOM'ify hw/char devices
Date: Wed, 25 May 2016 11:03:44 +0200 [thread overview]
Message-ID: <524ccc496f7e119359bd59a3ca3d1f7e@walle.cc> (raw)
In-Reply-To: <1464158344-12266-1-git-send-email-zxq_yx_007@163.com>
Am 2016-05-25 08:38, schrieb xiaoqiang zhao:
> This patch set trys to QOM'ify hw/char files, see commit messages
> for more details
>
> Thanks Paolo <pbonzini@redhat.com> for your suggestions.
>
> Note:
> * CRIS axis_dev88 broad related test is passed and looks ok.
> * lm32 test cases by Michael <michael@walle.cc> is passed and looks
> good.
> * lm32 milkymist need test by Michael.
>
> Changes in v6:
> * change lm32_juart_init to accept CharDriverState pointer as a
> parameter
> * QOM'ify milkymist-uart to drop qemu_char_get_next_serial
>
> Changes in v5:
> drop the call of qemu_char_get_next_serial in board code and
> direct access serial_hds array
>
> Changes in v4:
> * add wrapper functions to create char device
> * drop the sysbus_create_simple function and
> use the new qdev_create stuff
>
> Changes in v3:
> * use chardev property instead of qemu_char_get_next_serial
> * call the functions that touch globals in the realize callback
>
> xiaoqiang zhao (5):
> hw/char: QOM'ify escc.c
> hw/char: QOM'ify etraxfs_ser.c
> hw/char: QOM'ify lm32_juart.c
> hw/char: QOM'ify lm32_uart.c
> hw/char: QOM'ify milkymist-uart.c
Paolo, do you add this series to your queue?
-michael
next prev parent reply other threads:[~2016-05-25 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 6:38 [Qemu-devel] [PATCH v6 0/5] QOM'ify hw/char devices xiaoqiang zhao
2016-05-25 6:39 ` [Qemu-devel] [PATCH v6 1/5] hw/char: QOM'ify escc.c xiaoqiang zhao
2016-05-25 6:39 ` [Qemu-devel] [PATCH v6 2/5] hw/char: QOM'ify etraxfs_ser.c xiaoqiang zhao
2016-05-25 6:39 ` [Qemu-devel] [PATCH v6 3/5] hw/char: QOM'ify lm32_juart.c xiaoqiang zhao
2016-05-25 8:48 ` Michael Walle
2016-05-25 6:39 ` [Qemu-devel] [PATCH v6 4/5] hw/char: QOM'ify lm32_uart.c xiaoqiang zhao
2016-05-25 6:39 ` [Qemu-devel] [PATCH v6 5/5] hw/char: QOM'ify milkymist-uart.c xiaoqiang zhao
2016-05-25 8:49 ` Michael Walle
2016-05-25 8:20 ` [Qemu-devel] [PATCH v6 0/5] QOM'ify hw/char devices Paolo Bonzini
2016-05-25 9:03 ` Michael Walle [this message]
2016-05-25 9:06 ` Paolo Bonzini
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=524ccc496f7e119359bd59a3ca3d1f7e@walle.cc \
--to=michael@walle.cc \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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).