From: Marcel Apfelbaum <marcel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
kevin@koconnor.net, kraxel@redhat.com
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Delaying -rc0?
Date: Tue, 03 Mar 2015 17:07:09 +0200 [thread overview]
Message-ID: <54F5CE1D.7050802@redhat.com> (raw)
In-Reply-To: <54F5BDD5.5070706@redhat.com>
On 03/03/2015 03:57 PM, Paolo Bonzini wrote:
>
>
> On 03/03/2015 14:12, Marcel Apfelbaum wrote:
>> On 03/02/2015 03:11 PM, Paolo Bonzini wrote:
>>>
>>>
>>> On 02/03/2015 13:44, Peter Maydell wrote:
>>>> On 2 March 2015 at 21:33, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>>> Looks like there are still a few pull requests pending, and Peter is on
>>>>> vacation. Should we really enter hard feature freeze tomorrow? The
>>>>> 2.3
>>>>> planning page in the end never got out the "draft" state.
>>>>
>>>> Well, I said you probably didn't want to schedule rc0 for
>>>> while I was on holiday, but nobody changed the dates...
>>>>
>>>> My current intention is just to keep applying pullreqs
>>>> and then to look again at where we are once I'm back at
>>>> work. There are almost certainly pending ARM patches
>>>> which I need to assemble into a pullreq too.
>>>>
>>>>> A possible alternative schedule could be:
>>>>>
>>>>> 2015-03-10 Tag v2.3.0-rc0
>>>>
>>>> Hugely optimistic. I'm not likely to tag rc0 my first day
>>>> back at work :-)
>> Good!
>>
>> I want the "multi pci root buses" feature to get in 2.3 and is depending
>> on Igor's dynamic ACPI series that is still waiting in the PULL request.
>
> QEMU 2.3's SeaBIOS is already frozen to 1.8.0. Does it have the
> required support?
Hi Paolo,
(CCed Kevin and Gerd)
Well, the support was ready in time, see:
[SeaBIOS] [PATCH V3 0/2] fw/pci: better support for multiple host bridges
http://permalink.gmane.org/gmane.comp.bios.coreboot.seabios/8681
but the SeaBIOS maintainers preferred to see first the QEMU submission
getting accepted.
In the mean time this series depends on Igor's ACPI dynamic series that took
a lot of time to review and even Michael's PULL request with it is not yet in master.
The latest version is fully functional, the only reason is marked as 'RFC" is because
of the ACPI series API kept changing.
I will submit in a day or two the another version rebased on Michael's for_upstream tag.
(I was waiting for it to get in master...)
I really want to see this series into 2.3, please advise.
Thanks,
Marcel
>
> Paolo
>
next prev parent reply other threads:[~2015-03-03 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 12:33 [Qemu-devel] Delaying -rc0? Paolo Bonzini
2015-03-02 12:44 ` Peter Maydell
2015-03-02 13:11 ` Paolo Bonzini
2015-03-03 13:12 ` Marcel Apfelbaum
2015-03-03 13:57 ` Paolo Bonzini
2015-03-03 14:57 ` Gerd Hoffmann
2015-03-03 15:07 ` Marcel Apfelbaum [this message]
2015-03-03 15:14 ` Peter Maydell
2015-03-04 7:27 ` Markus Armbruster
2015-03-04 12:13 ` Gerd Hoffmann
2015-03-04 12:19 ` Michael S. Tsirkin
2015-03-04 12:26 ` Michael S. Tsirkin
2015-03-04 16:48 ` Markus Armbruster
2015-03-04 17:20 ` Michael S. Tsirkin
2015-03-04 12:08 ` Gerd Hoffmann
2015-03-02 21:42 ` Stefan Hajnoczi
2015-03-03 13:37 ` Michael S. Tsirkin
2015-03-04 7:27 ` Markus Armbruster
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=54F5CE1D.7050802@redhat.com \
--to=marcel@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@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.