From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
peter.maydell@linaro.org, vsementsov@virtuozzo.com,
"open list:qcow2" <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH for 4.2-rc5 1/1] block/qcow2-bitmap: fix crash bug in qcow2_co_remove_persistent_dirty_bitmap
Date: Mon, 9 Dec 2019 16:01:34 -0600 [thread overview]
Message-ID: <5d64f01e-aa1e-d5a7-06d9-73655ad3b36b@redhat.com> (raw)
In-Reply-To: <aa4571a2-2386-a9f0-a9a2-a51dbf6b146f@redhat.com>
On 12/9/19 11:03 AM, John Snow wrote:
> Did you mean to mark this as [PULL] ?
Probably - that's the curse of hand-editing a mail sent in-reply-to the
cover letter after the fact, instead of sending a v2 of the overall pull
request. At any rate, the correct commit made it in (f56281abd9).
>
> On 12/9/19 11:16 AM, Eric Blake wrote:
>> From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>
>> Here is double bug:
>>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-12-09 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 16:00 [PULL for 4.2-rc5 0/1] Bitmap fix for 2019-12-09 Eric Blake
2019-12-09 16:00 ` [PULL 1/1] pseries: Update SLOF firmware image Eric Blake
2019-12-09 16:13 ` Eric Blake
2019-12-09 16:13 ` Greg Kurz
2019-12-09 16:16 ` [PATCH for 4.2-rc5 1/1] block/qcow2-bitmap: fix crash bug in qcow2_co_remove_persistent_dirty_bitmap Eric Blake
2019-12-09 17:03 ` John Snow
2019-12-09 22:01 ` Eric Blake [this message]
2019-12-09 17:12 ` [PULL for 4.2-rc5 0/1] Bitmap fix for 2019-12-09 Peter Maydell
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=5d64f01e-aa1e-d5a7-06d9-73655ad3b36b@redhat.com \
--to=eblake@redhat.com \
--cc=jsnow@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=vsementsov@virtuozzo.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).