From: Gerd Hoffmann <kraxel@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kevin@koconnor.net, qemu-devel <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] Delaying -rc0?
Date: Wed, 04 Mar 2015 13:08:05 +0100 [thread overview]
Message-ID: <1425470885.8389.43.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <54F5CE1D.7050802@redhat.com>
Hi,
> 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.
Yep, that is the usual protocol to avoid ending up with stale code in
seabios because the qemu patches never make it upstream.
I havn't seen major objections on the RfC series, so I think it is ok to
go ahead committing the seabios patches when the dependencies are
merged, we have a non-rfc patch submission, and there is agreement this
is going to be merged for 2.3. That way we can parallelize the qemu and
seabios side of things a bit, to get both ready in time for -rc0.
> 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.
That's the real blocking thing here ...
cheers,
Gerd
next prev parent reply other threads:[~2015-03-04 12:08 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
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 [this message]
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=1425470885.8389.43.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=kevin@koconnor.net \
--cc=marcel@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 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).