From: Kevin Wolf <kwolf@redhat.com>
To: Xiaodong Gong <gordongong0350@gmail.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Fix improper usage of cpu_to_be32 in vpc
Date: Mon, 8 Sep 2014 17:34:59 +0200 [thread overview]
Message-ID: <20140908153459.GI4297@noname.redhat.com> (raw)
In-Reply-To: <1410187244-8266-1-git-send-email-gordon@localhost.localdomain>
Am 08.09.2014 um 16:40 hat Xiaodong Gong geschrieben:
> From: Xiaodong Gong <gordongong0350@gmail.com>
>
> cpu_to_be32() is wrong since vhd_type is an enum constant
> (just a regular CPU-endian integer).
>
> Signed-off-by: Xiaodong Gong <gordongong0350@gmail.com>
Thanks, this one is perfect. :-) Applied to the block branch.
Kevin
next prev parent reply other threads:[~2014-09-08 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 14:40 [Qemu-devel] [PATCH] Fix improper usage of cpu_to_be32 in vpc Xiaodong Gong
2014-09-08 15:34 ` Kevin Wolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-05 18:40 21G
2014-09-08 11:10 ` Kevin Wolf
2014-09-04 14:43 Gordon Gong
2014-09-05 10:04 ` Stefan Hajnoczi
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=20140908153459.GI4297@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=gordongong0350@gmail.com \
--cc=qemu-devel@nongnu.org \
--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).