From: John Levon <john.levon@nutanix.com>
To: Jag Raman <jag.raman@oracle.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
"clg@redhat.com" <clg@redhat.com>
Subject: Re: [PATCH] Mark Multi-Process QEMU as Orphaned
Date: Fri, 8 May 2026 15:37:46 +0100 [thread overview]
Message-ID: <af31Oo6gXE69c7eb@lent> (raw)
In-Reply-To: <IA4PR10MB83013C640DBB740BE8872FE4903D2@IA4PR10MB8301.namprd10.prod.outlook.com>
On Fri, May 08, 2026 at 02:33:59PM +0000, Jag Raman wrote:
>> QEMU maintainers can correct me, but I'd think it has to go through a
>> deprecation cycle first?
>
> If the code has to soak in a deprecated state, I think an “Obsolete” status
> better fits it as it’s replaced by vfio-user.
Are you saying you and/or Elena are still maintaining the vfio-user
implementation in hw/remote ? As I don't think there's anything happening there
either.
regards
john
next prev parent reply other threads:[~2026-05-08 14:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 10:26 [PATCH] Mark Multi-Process QEMU as Orphaned John Levon
2026-05-08 10:31 ` Peter Maydell
2026-05-08 10:35 ` John Levon
2026-05-08 10:43 ` Peter Maydell
2026-05-08 10:48 ` Philippe Mathieu-Daudé
2026-05-08 14:21 ` Jag Raman
2026-05-08 14:28 ` John Levon
2026-05-08 14:33 ` Jag Raman
2026-05-08 14:37 ` John Levon [this message]
2026-05-08 15:07 ` Jagannathan Raman
2026-05-08 15:19 ` John Levon
2026-05-08 15:35 ` Jagannathan Raman
2026-05-08 16:07 ` John Levon
2026-05-21 8:24 ` Cédric Le Goater
2026-05-21 14:41 ` Jag Raman
2026-05-11 16:15 ` Jag Raman
2026-05-11 16:25 ` John Levon
2026-05-11 16:39 ` Jag Raman
2026-05-22 20:48 ` Jag Raman
2026-05-26 9:04 ` John Levon
2026-05-26 15:36 ` Jag Raman
2026-05-08 14:39 ` Peter Maydell
2026-05-08 15:05 ` Daniel P. Berrangé
2026-05-08 18:28 ` Paolo Bonzini
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=af31Oo6gXE69c7eb@lent \
--to=john.levon@nutanix.com \
--cc=clg@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=qemu-devel@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.