From: Paolo Bonzini <pbonzini@redhat.com>
To: Li Qiang <liq3ea@gmail.com>, Li Qiang <liq3ea@163.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Jiri Slaby" <jslaby@suse.cz>,
"Qemu Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] hw: edu: some fixes
Date: Wed, 22 May 2019 10:29:35 +0200 [thread overview]
Message-ID: <e278d0cc-df8d-01c6-df02-79757134d35a@redhat.com> (raw)
In-Reply-To: <CAKXe6SLe1_ppEACqKVesvfrieN=c28rj9ro_xSGZ6F=Rf7iWew@mail.gmail.com>
On 21/05/19 15:30, Li Qiang wrote:
> Ping....
>
> Paolo, could you merge these to your misc tree?
Queued now, thanks.
Paolo
> Thanks,
> Li Qiang
>
> Li Qiang <liq3ea@163.com <mailto:liq3ea@163.com>> 于2019年5月11日周六 上
> 午12:44写道:
>
> Recently I am considering write a driver for edu device.
> After reading the spec, I found these three small issue.
> Two first two related the MMIO access and the third is
> related the DMA operation.
>
> Change since v2:
> Fix an error in patch 2
> Fix some commit message and title.
>
> Change since v1:
> Fix format compile error
>
> Li Qiang (3):
> edu: mmio: allow 64-bit access
> edu: mmio: allow 64-bit access in read dispatch
> edu: uses uint64_t in dma operation
>
> hw/misc/edu.c | 32 +++++++++++++++++++++++---------
> 1 file changed, 23 insertions(+), 9 deletions(-)
>
> --
> 2.17.1
>
>
prev parent reply other threads:[~2019-05-22 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 16:43 [Qemu-devel] [PATCH v4 0/3] hw: edu: some fixes Li Qiang
2019-05-10 16:43 ` [Qemu-devel] [PATCH v4 1/3] edu: mmio: allow 64-bit access Li Qiang
2019-05-10 16:43 ` [Qemu-devel] [PATCH v4 2/3] edu: mmio: allow 64-bit access in read dispatch Li Qiang
2019-05-10 16:43 ` [Qemu-devel] [PATCH v4 3/3] edu: uses uint64_t in dma operation Li Qiang
2019-05-22 11:01 ` Philippe Mathieu-Daudé
2019-05-10 23:53 ` [Qemu-devel] [PATCH v4 0/3] hw: edu: some fixes Peter Xu
2019-05-11 0:40 ` Li Qiang
2019-05-21 13:30 ` Li Qiang
2019-05-22 8:29 ` Paolo Bonzini [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=e278d0cc-df8d-01c6-df02-79757134d35a@redhat.com \
--to=pbonzini@redhat.com \
--cc=jslaby@suse.cz \
--cc=liq3ea@163.com \
--cc=liq3ea@gmail.com \
--cc=philmd@redhat.com \
--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).