qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] Next release
Date: Sun, 7 Jul 2013 18:50:44 +0300	[thread overview]
Message-ID: <20130707155044.GA8816@redhat.com> (raw)
In-Reply-To: <20130707151403.GA27321@morn.localdomain>

On Sun, Jul 07, 2013 at 11:14:03AM -0400, Kevin O'Connor wrote:
> On Sun, Jul 07, 2013 at 06:01:08PM +0300, Michael S. Tsirkin wrote:
> > On Mon, Jul 01, 2013 at 05:20:46PM -0400, Kevin O'Connor wrote:
> > > As previously discussed, I'll be generating the next seabios release
> > > in the next couple of days.  If there are any outstanding defects that
> > > need to be addressed in this release, please let me know.
> > > 
> > > -Kevin
> > 
> > Could you also include the patch that
> > loads the PCI config from qemu?
> 
> Lets add that to the next release.  We can create a new stable release
> if needed.
> 
> -Kevin

Hmm ... do you think this and loading acpi tables from
qemu are reasonable things to add to a stable release?

For QEMU the plan is to tag 1.6.0-rc1 on Aug 1,
and naturally we will only use a stable seabios there
http://wiki.qemu.org/Planning/1.6

Hard freeze is a month from now, and things work fine
for me so I was hoping to start loading acpi
from qemu in that version. Is there a way to
have some seabios release that supports this in time
for 1.6?

-- 
MST

  reply	other threads:[~2013-07-07 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130701212046.GA12564@morn.localdomain>
2013-07-07 15:01 ` [Qemu-devel] [SeaBIOS] Next release Michael S. Tsirkin
2013-07-07 15:14   ` Kevin O'Connor
2013-07-07 15:50     ` Michael S. Tsirkin [this message]
2013-07-08  1:00       ` Kevin O'Connor

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=20130707155044.GA8816@redhat.com \
    --to=mst@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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).