All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	Igor Mammedov <imammedo@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL for-2.1 0/3] Last minute patches
Date: Mon, 28 Jul 2014 14:59:26 +0200	[thread overview]
Message-ID: <87a97twsep.fsf@troll.troll> (raw)
In-Reply-To: <CAFEAcA8oxJtVJ6AwgqTX5R-3x3MhmpT+RysFHG_assHR6tGvpg@mail.gmail.com> (Peter Maydell's message of "Fri, 25 Jul 2014 17:00:35 +0100")

Peter Maydell <peter.maydell@linaro.org> wrote:
> On 25 July 2014 15:22, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Since Igor hasn't sent his patches, and I'm leaving the office, I pushed
>> this to
>>
>>    git://github.com/bonzini/qemu.git tags/for-upstream-full
>>
>> I don't know about tests/acpi-test-data/pc.  It makes sense that this
>> patch should modify something there, but:
>>
>> * "make check" passes
>>
>> * the test warns even before patch 1, for both the DSDT (modified by the
>> patch) and SSDT (which this series doesn't touch at all)
>>
>> * I cannot get it to pass, except by blindly copying the "actual" output
>> on the "expected" files
>>
>> * mst is on vacation and Marcel is off on Fridays
>>
>> Based on my understanding of the problem, it is not possible to fix the
>> bug without hacks like this one, and even reverting all patches in this
>> area would be more risky.
>
> Hmm. I'm not really sure what the right thing is, so what
> I'm planning to do is:
>  * just apply the qemu-char fix for now
>  * not tag -rc4 today
>  * see if things are clearer on Monday (I see Igor has now
>    sent out a patchset)
>  * tag -rc4 Mon or Tues
>  * slip the release date a few days (not a big deal, I think)

I am reading both patch-sets.

I preffer very much Paolo solution to Igor one.

But I have to say that I don't understand PATCH 1 (neither before or
after the change).  Solution does what we should do, that is generate
the size that destination is expecting, and no simply blindy accept
packages that are smaller.

The compatibility bits of PATCH2 look ok (that ones, I can kind of
understand them).


Igor?

Later, Juan.

  reply	other threads:[~2014-07-28 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 12:15 [Qemu-devel] [PULL for-2.1 0/3] Last minute patches Paolo Bonzini
2014-07-25 12:15 ` [Qemu-devel] [PULL 1/3] acpi-dsdt: procedurally generate _PRT Paolo Bonzini
2014-07-25 12:15 ` [Qemu-devel] [PULL 2/3] pc: hack for migration compatibility from QEMU 2.0 Paolo Bonzini
2014-07-25 12:16 ` [Qemu-devel] [PULL 3/3] qemu-char: ignore flow control if a PTY's slave is not connected Paolo Bonzini
2014-07-25 14:22 ` [Qemu-devel] [PULL for-2.1 0/3] Last minute patches Paolo Bonzini
2014-07-25 16:00   ` Peter Maydell
2014-07-28 12:59     ` Juan Quintela [this message]
2014-07-28 13:31       ` Igor Mammedov

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=87a97twsep.fsf@troll.troll \
    --to=quintela@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 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.