qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] Memory API conversions, batch 5
Date: Thu, 25 Aug 2011 22:24:37 +0300	[thread overview]
Message-ID: <4E56A175.30300@redhat.com> (raw)
In-Reply-To: <CAAu8pHs_3akbDCgUmipjZztGqmcjBdmO1zaGbmhAVyko5E0rpA@mail.gmail.com>

On 08/25/2011 09:58 PM, Blue Swirl wrote:
> >
> >  Guys, please start testing before applying these patches. It's not hard,
> >  there are images on the wiki with scripts that area easy to run.
>
> It's also possible to revert offending patches.

Please revert the entire pull (git revert 8ef9ea85a2cc1) while I work 
this out - it isn't trivial.

> But a better solution
> would be to have a comprehensive test setup to do builds and run
> checks on selected trees. Before a pull to main tree, the test results
> should be available.
>

True, we should be able to get kvm-autotest to do a sanity test.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  parent reply	other threads:[~2011-08-25 19:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  8:01 [Qemu-devel] [PULL] Memory API conversions, batch 5 Avi Kivity
2011-08-25 13:04 ` Anthony Liguori
2011-08-25 18:27   ` Edgar E. Iglesias
2011-08-25 18:58     ` Blue Swirl
2011-08-25 19:02       ` Anthony Liguori
2011-08-25 19:16         ` Blue Swirl
2011-08-31  6:30           ` Markus Armbruster
2011-08-25 19:17         ` Edgar E. Iglesias
2011-08-25 19:24       ` Avi Kivity [this message]
2011-08-25 19:32     ` Jan Kiszka
2011-08-25 19:36       ` Avi Kivity
2011-08-25 19:38         ` Jan Kiszka

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=4E56A175.30300@redhat.com \
    --to=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).