From: Gerd Hoffmann <kraxel@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Kevin O'Connor <kevin@koconnor.net>,
seabios <seabios@seabios.org>,
xen-devel <xen-devel@lists.xenproject.org>,
qemu-devel <qemu-devel@nongnu.org>, paul <paul@xen.org>
Subject: Re: [SeaBIOS] Re: [SeaBIOS PATCH] xen: require Xen info structure at 0x1000 to detect Xen
Date: Thu, 2 Feb 2023 10:10:31 +0100 [thread overview]
Message-ID: <20230202091031.xmnao56wziptjak2@sirius.home.kraxel.org> (raw)
In-Reply-To: <fd3259a2765d4b33ccf7baea320ac798bab63159.camel@infradead.org>
> Thanks, Kevin.
>
> I'd like to get the rest of the Xen platform support in to qemu 8.0 if
> possible. Which is currently scheduled for March.
>
> Is there likely to be a SeaBIOS release before then which Gerd would
> pull into qemu anyway, or should I submit a submodule update to a
> snapshot of today's tree? That would just pull in this commit, and the
> one other fix that's in the SeaBIOS tree since 1.16.1?
Tagging 1.16.2 in time for the qemu 8.0 should not be a problem given
that we have only bugfixes in master. Roughly around soft freeze is
probably a good time for that.
take care,
Gerd
next prev parent reply other threads:[~2023-02-02 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 11:33 [SeaBIOS PATCH] xen: require Xen info structure at 0x1000 to detect Xen David Woodhouse
2023-01-26 17:49 ` Paul Durrant
2023-01-26 23:52 ` [SeaBIOS] " Kevin O'Connor
2023-02-02 2:13 ` Kevin O'Connor
2023-02-02 8:05 ` David Woodhouse
2023-02-02 9:10 ` Gerd Hoffmann [this message]
2023-03-07 8:42 ` [SeaBIOS] " David Woodhouse
2023-03-09 11:27 ` Gerd Hoffmann
2023-03-16 13:02 ` seabios 1.16.2 release tagged (was: Re: [SeaBIOS] Re: [SeaBIOS PATCH] xen: require Xen info structure at). " Gerd Hoffmann
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=20230202091031.xmnao56wziptjak2@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dwmw2@infradead.org \
--cc=kevin@koconnor.net \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=xen-devel@lists.xenproject.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).