From: Jagannathan Raman <jag.raman@oracle.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, armbru@redhat.com, elena.ufimtseva@oracle.com
Subject: [PATCH v1 0/2] Fix the documentation for vfio-user and multi-process QEMU
Date: Wed, 17 May 2023 16:43:55 +0000 [thread overview]
Message-ID: <cover.1684338236.git.jag.raman@oracle.com> (raw)
This series addresses recent comments from Markus Armbruster in the
"Machine x-remote property auto-shutdown" email thread.
Jagannathan Raman (2):
vfio-user: update comments
docs: fix multi-process QEMU documentation
docs/system/multi-process.rst | 2 +-
hw/remote/vfio-user-obj.c | 14 +++++++++++---
2 files changed, 12 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2023-05-17 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 16:43 Jagannathan Raman [this message]
2023-05-17 16:43 ` [PATCH v1 1/2] vfio-user: update comments Jagannathan Raman
2023-05-25 15:02 ` Markus Armbruster
2023-05-25 17:59 ` Stefan Hajnoczi
2023-05-17 16:43 ` [PATCH v1 2/2] docs: fix multi-process QEMU documentation Jagannathan Raman
2023-05-25 15:02 ` Markus Armbruster
2023-05-25 17:59 ` [PATCH v1 0/2] Fix the documentation for vfio-user and multi-process QEMU Stefan Hajnoczi
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=cover.1684338236.git.jag.raman@oracle.com \
--to=jag.raman@oracle.com \
--cc=armbru@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).