From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, qemu-stable@nongnu.org,
Michael Tokarev <mjt@tls.msk.ru>
Cc: Greg Kurz <groug@kaod.org>, Feifan Qian <bea1e@proton.me>
Subject: Re: [PATCH 0/3] 9pfs: fix invalid union V9fsFidOpenState access
Date: Wed, 17 Jun 2026 13:49:46 +0200 [thread overview]
Message-ID: <7957233.EvYhyI6sBW@weasel> (raw)
In-Reply-To: <7735fc49-6669-43c7-b367-669cb88b2c8f@tls.msk.ru>
On Wednesday, 17 June 2026 12:43:09 CEST Michael Tokarev wrote:
> On 17.06.2026 12:59, Christian Schoenebeck wrote:
[...]
> > What about delaying the stable release for a week? Does that sound like a
> > viable compromise?
>
> Let's make it into the next stable releases instead. You can include
> the set which is already published in your tree, and for the rest, let's
> wait for the next round. I don't plan to delay next stable releases.
Agreed.
The already queued 3 patches will certainly make it to master in-time for the
stable release next week, but all other patches will miss that release window.
Thanks!
/Christian
prev parent reply other threads:[~2026-06-17 11:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 15:00 [PATCH 0/3] 9pfs: fix invalid union V9fsFidOpenState access Christian Schoenebeck
2026-06-16 15:00 ` [PATCH 2/3] hw/9pfs: fix invalid union access by v9fs_co_fstat() Christian Schoenebeck
2026-06-16 15:00 ` [PATCH 3/3] hw/9pfs/local: harden local_fid_fd() on FID types Christian Schoenebeck
2026-06-16 15:00 ` [PATCH 1/3] hw/9pfs: fix invalid union access by v9fs_co_fsync() Christian Schoenebeck
2026-06-17 7:27 ` [PATCH 0/3] 9pfs: fix invalid union V9fsFidOpenState access Michael Tokarev
2026-06-17 8:10 ` Christian Schoenebeck
2026-06-17 9:35 ` Michael Tokarev
2026-06-17 9:59 ` Christian Schoenebeck
2026-06-17 10:43 ` Michael Tokarev
2026-06-17 11:49 ` Christian Schoenebeck [this message]
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=7957233.EvYhyI6sBW@weasel \
--to=qemu_oss@crudebyte.com \
--cc=bea1e@proton.me \
--cc=groug@kaod.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.