From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Colin Lord <clord@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.8] dmg: Move the driver to block-obj-y
Date: Fri, 12 Aug 2016 09:30:44 +0800 [thread overview]
Message-ID: <20160812013044.GB2759@al.usersys.redhat.com> (raw)
In-Reply-To: <20160811024657.GA9358@al.usersys.redhat.com>
On Thu, 08/11 10:46, Fam Zheng wrote:
> If you apply this patch with the above two issues fixed, I'll send another
> patch to fix the last cast? Is that okay?
If we want to apply Corlin's series for dynamic loading, I'll need to rebase
anyway. Let's discuss or proceed in his other thread.
Fam
prev parent reply other threads:[~2016-08-12 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 8:01 [Qemu-devel] [PATCH for-2.8] dmg: Move the driver to block-obj-y Fam Zheng
2016-08-03 11:41 ` Paolo Bonzini
2016-08-10 18:30 ` Max Reitz
2016-08-11 2:46 ` Fam Zheng
2016-08-12 1:30 ` Fam Zheng [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=20160812013044.GB2759@al.usersys.redhat.com \
--to=famz@redhat.com \
--cc=clord@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).