From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>, Richie Buturla <richie@linux.ibm.com>,
Oliver Chang <ochang@google.com>,
qemu-stable <qemu-stable@nongnu.org>,
Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [PULL 0/2] 9p queue 2026-02-28
Date: Sun, 01 Mar 2026 15:46:30 +0100 [thread overview]
Message-ID: <5970717.DvuYhMxLoT@weasel> (raw)
In-Reply-To: <e73dbda1-f569-4299-a8a4-4d2ed1b943a9@tls.msk.ru>
On Sunday, 1 March 2026 07:23:43 CET Michael Tokarev wrote:
> On 28.02.2026 16:30, Christian Schoenebeck wrote:
> > 9pfs changes:
> > * Fix crash under unlink-heavy load in v9fs_mark_fids_unreclaim().
> > * Fix crash with the synth fs driver.
> >
> > ----------------------------------------------------------------
> >
> > Christian Schoenebeck (1):
> > hw/9pfs: fix missing EOPNOTSUPP on Twstat and Trenameat for fs
> > synth driver
> >
> > Richie Buturla (1):
> > hw/9pfs: fix data race in v9fs_mark_fids_unreclaim()
>
> Hi!
>
> I'm picking these changes up for active qemu stable releases,
> as these looks like bug fixes worth to have.
Yes, that makes sense.
> Please let me know if I shouldn't do that.
>
> Also, please Cc: qemu-stable for future patches which, in your
> opinion, should be back-ported to the stable releases.
I usually do. For some reason I have forgotten to CC qemu-stable this time.
Thanks for the reminder and noticing!
/Christian
next prev parent reply other threads:[~2026-03-01 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 13:30 [PULL 0/2] 9p queue 2026-02-28 Christian Schoenebeck
2026-02-28 13:30 ` [PULL 2/2] hw/9pfs: fix missing EOPNOTSUPP on Twstat and Trenameat for fs synth driver Christian Schoenebeck
2026-02-28 13:30 ` [PULL 1/2] hw/9pfs: fix data race in v9fs_mark_fids_unreclaim() Christian Schoenebeck
2026-03-01 6:23 ` [PULL 0/2] 9p queue 2026-02-28 Michael Tokarev
2026-03-01 14:46 ` Christian Schoenebeck [this message]
2026-03-01 11:20 ` Peter Maydell
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=5970717.DvuYhMxLoT@weasel \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=mjt@tls.msk.ru \
--cc=ochang@google.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richie@linux.ibm.com \
/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.