From: Leonid Bloch <lbloch@janustech.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "qemu-block@nongnu.org" <qemu-block@nongnu.org>,
Stefan Weil <sw@weilnetz.de>, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Leonid Bloch <lbloch@janustech.com>
Subject: [Qemu-devel] [PATCH v2 0/1] vdi: Use a literal number of bytes for
Date: Sun, 4 Nov 2018 18:09:26 +0000 [thread overview]
Message-ID: <20181104180900.7527-1-lbloch@janustech.com> (raw)
Please see the commit message for the rationale.
Difference from v1:
* Format string is fixed.
Leonid Bloch (1):
vdi: Use a literal number of bytes for DEFAULT_CLUSTER_SIZE
block/vdi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2018-11-04 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 18:09 Leonid Bloch [this message]
2018-11-04 18:09 ` [Qemu-devel] [PATCH v2 1/1] vdi: Use a literal number of bytes for DEFAULT_CLUSTER_SIZE Leonid Bloch
2018-11-04 19:10 ` Stefan Weil
2018-11-05 14:29 ` [Qemu-devel] [PATCH v2 0/1] vdi: Use a literal number of bytes for 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=20181104180900.7527-1-lbloch@janustech.com \
--to=lbloch@janustech.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).