Confidential - Oracle Restricted \Including External Recipients




Confidential - Oracle Restricted \Including External Recipients

From: John Levon <[email protected]>
Date: Friday, May 8, 2026 at 10:28 AM
To: Jag Raman <[email protected]>
Cc: [email protected] <[email protected]>; Elena Ufimtseva 
<[email protected]>; [email protected] <[email protected]>
Subject: Re: [PATCH] Mark Multi-Process QEMU as Orphaned

On Fri, May 08, 2026 at 02:21:37PM +0000, Jag Raman wrote:

> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0a90204ae9..ce2b494086 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4429,7 +4429,7 @@ F: tests/tcg/aarch64/system/semiheap.c
>  Multi-process QEMU
>  M: Elena Ufimtseva <[email protected]>
>  M: Jagannathan Raman <[email protected]>
> -S: Maintained
> +S: Orphan
>  F: docs/devel/multi-process.rst
>  F: docs/system/multi-process.rst
>  F: hw/pci-host/remote.c
>
> Thanks for the reminder, John!

(Just for context, Cédric suggested this after my patch to update the
libvfio-user submodule for the compilation issues.)

> I’ll send a PR shortly removing parts we are not longer using.

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.


regards
john

Reply via email to