qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>, Avi Kivity <avi@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] Memory API conversions, batch 5
Date: Thu, 25 Aug 2011 21:17:46 +0200	[thread overview]
Message-ID: <20110825191746.GD21302@zapo> (raw)
In-Reply-To: <4E569C40.3010609@redhat.com>

On Thu, Aug 25, 2011 at 02:02:24PM -0500, Anthony Liguori wrote:
> On 08/25/2011 01:58 PM, Blue Swirl wrote:
> >On Thu, Aug 25, 2011 at 6:27 PM, Edgar E. Iglesias
> ><edgar.iglesias@gmail.com>  wrote:
> >>On Thu, Aug 25, 2011 at 08:04:34AM -0500, Anthony Liguori wrote:
> >>>On 08/25/2011 03:01 AM, Avi Kivity wrote:
> >>>>Please pull from
> >>>>
> >>>>git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/batch
> >>>>
> >>>>to receive the fifth memory API conversions batch. There is really
> >>>>nothing notable, except perhaps the first use of the transaction API.
> >>>>
> >>>>While the patches have been on the list for just a short time, they have
> >>>>received quite extensive review, for which I am thankful.
> >>>
> >>>Pulled.  Thanks.
> >>
> >>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. 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.
> 
> Before a pull *request*.  Semantically, pull requests should be
> treated as a push.  It's the submaintainers responsibility to test
> the bits they do a pull request for.

Yup.

> That said, the logistics of testing a series like this is mind
> numbingly complex.  We really need to all work on better automation
> for this.  In the interim, I think we're just going to have to leave
> with occasional breakage from changes like this and make sure it
> doesn't happen too frequently.

Yes, I understand its not an easy to test all combinations. But there
are scripts that testrun various targets on the wiki. It doesnt take
long to run those. You can also explicitely ask for help with the testing.
I'm happy to assist if the test scripts dont run or if you CC me on
a testme request.

Avi's done a great job with these series, converting all targets and all.
I dont mean to misscredit that.

Cheers

  parent reply	other threads:[~2011-08-25 19:17 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 [this message]
2011-08-25 19:24       ` Avi Kivity
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=20110825191746.GD21302@zapo \
    --to=edgar.iglesias@gmail.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=blauwirbel@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).