From: Paolo Bonzini <pbonzini@redhat.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1] kvm: tolerate non-existing slot for log_start and log_stop
Date: Mon, 16 Oct 2017 14:14:07 +0200 [thread overview]
Message-ID: <59cacd65-007a-2381-31aa-b17a98d8bb0e@redhat.com> (raw)
In-Reply-To: <650c557c-4c1c-181e-75b5-bcb58ddb2746@redhat.com>
On 16/10/2017 11:53, David Hildenbrand wrote:
>
> Looks like adding these assertions was counter productive :)
Or productive. Bugs happen, and if they are a good occasion to add new
tests to the testsuite or at least a comment to the code, all the better.
Paolo
next prev parent reply other threads:[~2017-10-16 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 9:41 [Qemu-devel] [PATCH v1] kvm: tolerate non-existing slot for log_start and log_stop David Hildenbrand
2017-10-16 9:53 ` David Hildenbrand
2017-10-16 12:14 ` Paolo Bonzini [this message]
2017-10-16 12:13 ` Paolo Bonzini
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=59cacd65-007a-2381-31aa-b17a98d8bb0e@redhat.com \
--to=pbonzini@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).