From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Fam Zheng <famz@redhat.com>, qemu block <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [0 0/2] Block patches
Date: Mon, 29 Oct 2018 13:55:05 +0000 [thread overview]
Message-ID: <CAJSP0QWu-1m4ohmzrtjDUL+ArBUpZypbszsmPY2VFyqZWr9pWA@mail.gmail.com> (raw)
In-Reply-To: <20181029134123.3365-1-stefanha@redhat.com>
Sorry, this pull request came out wrong. I will resend.
Stefan
prev parent reply other threads:[~2018-10-29 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 13:41 [Qemu-devel] [0 0/2] Block patches Stefan Hajnoczi
2018-10-29 13:41 ` [Qemu-devel] [0 1/2] util: aio-posix: fix a typo Stefan Hajnoczi
2018-10-29 13:41 ` [Qemu-devel] [0 2/2] nvdimm: Add docs hint for Linux driver name Stefan Hajnoczi
2018-10-29 13:55 ` Stefan Hajnoczi [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=CAJSP0QWu-1m4ohmzrtjDUL+ArBUpZypbszsmPY2VFyqZWr9pWA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--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).