From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/7] block-vpc: Split up struct vpc_subheader
Date: Mon, 26 Jan 2009 14:27:09 -0600 [thread overview]
Message-ID: <497E1C9D.2020104@us.ibm.com> (raw)
In-Reply-To: <1232989168-27759-2-git-send-email-kwolf@suse.de>
Kevin Wolf wrote:
> struct vpc_subheader currently is a union of two completely different
> data structures (the Hard Disk Footer and the Dynamic Disk Header).
> That doesn't make too much sense, so split them up.
>
> Signed-off-by: Kevin Wolf <kwolf@suse.de>
>
Applied all. Thanks.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-01-26 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 16:59 [Qemu-devel] [PATCH 0/7] block-vpc: Improve support for VHD images Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 1/7] block-vpc: Split up struct vpc_subheader Kevin Wolf
2009-01-26 20:27 ` Anthony Liguori [this message]
2009-01-26 16:59 ` [Qemu-devel] [PATCH 2/7] block-vpc: Adapt header structures to official documentation Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 3/7] block-vpc: Fix disk size Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 4/7] block-vpc: Fix support for images > 4 GB Kevin Wolf
2009-01-27 11:03 ` Kevin Wolf
2009-01-27 14:30 ` Anthony Liguori
2009-01-27 14:29 ` Anthony Liguori
2009-01-26 16:59 ` [Qemu-devel] [PATCH 5/7] block-vpc: Use the qemu block layer Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 6/7] block-vpc: Write support Kevin Wolf
2009-01-26 16:59 ` [Qemu-devel] [PATCH 7/7] block-vpc: Create images Kevin Wolf
2009-01-26 21:52 ` [Qemu-devel] [PATCH 0/7] block-vpc: Improve support for VHD images Jamie Lokier
2009-01-27 9:20 ` Kevin Wolf
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=497E1C9D.2020104@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=kwolf@suse.de \
--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.