From: Stefan Hajnoczi <stefanha@redhat.com>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: qemu-devel@nongnu.org, "Greg Kurz" <groug@kaod.org>,
"Sean Wei" <me@sean.taipei>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PULL 0/2] 9p queue 2025-07-16
Date: Thu, 17 Jul 2025 16:56:24 -0400 [thread overview]
Message-ID: <20250717205624.GA378711@fedora> (raw)
In-Reply-To: <cover.1752669861.git.qemu_oss@crudebyte.com>
[-- Attachment #1: Type: text/plain, Size: 116 bytes --]
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/10.1 for any user-visible changes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-07-17 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 12:44 [PULL 0/2] 9p queue 2025-07-16 Christian Schoenebeck
2025-07-16 12:44 ` [PULL 1/2] fsdev/9p-marshal: move G_GNUC_PRINTF to header Christian Schoenebeck
2025-07-16 12:44 ` [PULL 2/2] hw/9pfs: " Christian Schoenebeck
2025-07-17 20:56 ` Stefan Hajnoczi [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=20250717205624.GA378711@fedora \
--to=stefanha@redhat.com \
--cc=groug@kaod.org \
--cc=me@sean.taipei \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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 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).