All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>, Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, borntraeger@de.ibm.com,
	frankja@linux.ibm.com, david@redhat.com, cohuck@redhat.com,
	thuth@redhat.com
Subject: Re: [PATCH 0/4] KVM: selftests: Various cleanups and fixes
Date: Sat, 14 Mar 2020 12:44:20 +0100	[thread overview]
Message-ID: <c6604237-2618-9f6f-a3ef-42ac195ca670@redhat.com> (raw)
In-Reply-To: <20200311192949.GL479302@xz-x1>

On 11/03/20 20:29, Peter Xu wrote:
> On Tue, Mar 10, 2020 at 10:15:52AM +0100, Andrew Jones wrote:
>>
>> Andrew Jones (4):
>>   fixup! selftests: KVM: SVM: Add vmcall test
>>   KVM: selftests: Share common API documentation
>>   KVM: selftests: Enable printf format warnings for TEST_ASSERT
>>   KVM: selftests: Use consistent message for test skipping
> 
> Reviewed-by: Peter Xu <peterx@redhat.com>
> 
> I'll rebase my further tests against this too.  Thanks!
> 

Queued, thanks.

Paolo


      reply	other threads:[~2020-03-15  3:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  9:15 [PATCH 0/4] KVM: selftests: Various cleanups and fixes Andrew Jones
2020-03-10  9:15 ` [PATCH 1/4] fixup! selftests: KVM: SVM: Add vmcall test Andrew Jones
2020-03-10  9:15 ` [PATCH 2/4] KVM: selftests: Share common API documentation Andrew Jones
2020-03-10  9:15 ` [PATCH 3/4] KVM: selftests: Enable printf format warnings for TEST_ASSERT Andrew Jones
2020-03-10 12:54   ` Christian Borntraeger
2020-03-10  9:15 ` [PATCH 4/4] KVM: selftests: Use consistent message for test skipping Andrew Jones
2020-03-10  9:45 ` [PATCH 0/4] KVM: selftests: Various cleanups and fixes Christian Borntraeger
2020-03-10 11:58   ` Andrew Jones
2020-03-10 12:29     ` Christian Borntraeger
2020-03-10 12:34       ` Christian Borntraeger
2020-03-10 13:18         ` Andrew Jones
2020-03-11 19:29 ` Peter Xu
2020-03-14 11:44   ` Paolo Bonzini [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=c6604237-2618-9f6f-a3ef-42ac195ca670@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=peterx@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.