From: Sheng Yang <sheng@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Naphtali Sprei <nsprei@redhat.com>,
Christoph Hellwig <hch@lst.de>, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2 resend 0/4] block: more read-only changes, related to backing files
Date: Fri, 5 Feb 2010 10:46:41 +0800 [thread overview]
Message-ID: <201002051046.41334.sheng@linux.intel.com> (raw)
In-Reply-To: <1265321069-4105-1-git-send-email-nsprei@redhat.com>
On Friday 05 February 2010 06:04:25 Naphtali Sprei wrote:
> This is version 2. The change between previous patch (only 3/4) is the
> order of closing/re-opening the image.
>
> Naphtali Sprei (4):
> Add open_flags to BlockDriverState Will be used later
> qemu-img: Fix qemu-img can't create qcow image based on read-only
> image
> Block: readonly changes
> Open backing file read-only also for snapshot mode
>
(CC to the original reviewers...)
--
regards
Yang, Sheng
prev parent reply other threads:[~2010-02-05 2:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 22:04 [Qemu-devel] [PATCH v2 resend 0/4] block: more read-only changes, related to backing files Naphtali Sprei
2010-02-04 22:04 ` [Qemu-devel] [PATCH v2 resend 1/4] Add open_flags to BlockDriverState Will be used later Naphtali Sprei
2010-02-04 22:04 ` [Qemu-devel] [PATCH v2 resend 2/4] qemu-img: Fix qemu-img can't create qcow image based on read-only image Naphtali Sprei
2010-02-04 22:04 ` [Qemu-devel] [PATCH v2 resend 3/4] Block: readonly changes Naphtali Sprei
2010-02-04 22:04 ` [Qemu-devel] [PATCH v2 resend 4/4] Open backing file read-only also for snapshot mode Naphtali Sprei
2010-02-05 8:20 ` [Qemu-devel] [PATCH v2 resend 3/4] Block: readonly changes Kevin Wolf
2010-02-05 2:45 ` [Qemu-devel] [PATCH v2 resend 2/4] qemu-img: Fix qemu-img can't create qcow image based on read-only image Sheng Yang
2010-02-05 2:46 ` Sheng Yang [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=201002051046.41334.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=agraf@suse.de \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=nsprei@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.