qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com, rth@twiddle.net
Subject: [Qemu-devel] [PATCH v2 0/4] block: use QEMU_PACKED for on-disk structures
Date: Wed, 25 Sep 2013 12:08:47 -0400	[thread overview]
Message-ID: <cover.1380124547.git.jcody@redhat.com> (raw)

v2 changes:
Dropped the "cow" format patch.  This means "cow" is non-portable, but
it keeps behavior the same on x86_64. (Richard Henderson)

Moved QEMU_PACKED to after the struct definition closing brace, to keep it more
stylistically in-line with other QEMU_PACKED useage (Kevin Wolf)

Original description:

Several block image formats did not consistently use packed attributes
when directly reading / writing structures from disk (mainly image format
headers).

These series updates the image formats (see list below), to use
QEMU_PACKED for on-disk structs.  (Some minor code cleanup may also
have ensued, to keep checkpatch.pl happy)


Jeff Cody (4):
  block: vdi - use QEMU_PACKED for on-disk structures
  block: vpc - use QEMU_PACKED for on-disk structures
  block: qcow2 - used QEMU_PACKED for on-disk structures
  block: qed - use QEMU_PACKED for on-disk structures

 block/qcow2.c |  2 +-
 block/qcow2.h |  2 +-
 block/qed.h   |  2 +-
 block/vdi.c   |  2 +-
 block/vpc.c   | 28 ++++++++++++++--------------
 5 files changed, 18 insertions(+), 18 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2013-09-25 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 16:08 Jeff Cody [this message]
2013-09-25 16:08 ` [Qemu-devel] [PATCH v2 1/4] block: vdi - use QEMU_PACKED for on-disk structures Jeff Cody
2013-09-25 16:08 ` [Qemu-devel] [PATCH v2 2/4] block: vpc " Jeff Cody
2013-09-25 16:08 ` [Qemu-devel] [PATCH v2 3/4] block: qcow2 - used " Jeff Cody
2013-09-25 16:08 ` [Qemu-devel] [PATCH v2 4/4] block: qed - use " Jeff Cody
2013-09-25 16:32 ` [Qemu-devel] [PATCH v2 0/4] block: " Richard Henderson
2013-09-25 18:51   ` 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=cover.1380124547.git.jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.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).