From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "seabios@seabios.org" <seabios@seabios.org>,
"mark.cave-ayland@ilande.co.uk" <mark.cave-ayland@ilande.co.uk>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [SeaBIOS] new release tag?
Date: Fri, 8 Sep 2023 09:58:22 +0000 [thread overview]
Message-ID: <ZPrwOo6KVPk7N6yq@x1-carbon> (raw)
In-Reply-To: <ifi2dswo3cuqquzqiys7jamlvefaoxmvobljqotrh63xzceld6@ndbqfrnp762a>
On Thu, Aug 24, 2023 at 10:56:05AM +0200, Gerd Hoffmann wrote:
> On Mon, Aug 07, 2023 at 10:51:33AM +0000, Niklas Cassel via SeaBIOS wrote:
> > Hello Seabios maintainers,
> >
> >
> > I was wondering, is there any chance of getting a new release tag
> > (e.g. rel-1.16.3) anytime soon?
> > Or is there any plan on when it will be tagged?
> >
> > I'm waiting to send out a (AHCI specific) QEMU patch, but I can't
> > do so until:
> > 1) there is a new Seabios tag
> > 2) QEMU has updated to the latest Seabios release tag
>
> I guess Mark (Cc'ed) is sitting in the same boat with the scsi
> driver fixes.
>
> We just missed qemu 8.1, so we don't have to rush things,
> but it probably makes sense to update seabios not too late
> in the 8.2 devel cycle due to qemu patches depending on the
> seabios fixes.
>
> Cc'ing qemu-devel: Are there any qemu changes pending or
> planned for 8.2 which need changes in seabios?
Hello Gerd,
The QEMU 8.2 devel cycle has started.
I do not want to stress you, but if we want to get additional fixes in,
that depend on the new seabios version, isn't it better to get the new
seabios version included sooner rather than later?
Kind regards,
Niklas
next prev parent reply other threads:[~2023-09-08 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZNDMtAeAGJardllS@x1-carbon>
2023-08-24 8:56 ` [SeaBIOS] new release tag? Gerd Hoffmann
2023-09-08 9:58 ` Niklas Cassel [this message]
2023-09-12 10:41 ` [SeaBIOS] " 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=ZPrwOo6KVPk7N6yq@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=kraxel@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).