From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yosry Ahmed <yosry@kernel.org>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oupton@kernel.org>,
Tianrui Zhao <zhaotianrui@loongson.cn>,
Bibo Mao <maobibo@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Anup Patel <anup@brainfault.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Subject: Re: [RFC PATCH 4/5] MAINTAINERS: Add David H. as a KVM guest_memfd reviewer
Date: Tue, 28 Apr 2026 21:27:43 +0200 [thread overview]
Message-ID: <d6a90fc2-baf8-47a9-bda8-c21e55523677@kernel.org> (raw)
In-Reply-To: <20260428171541.1342335-5-seanjc@google.com>
On 4/28/26 19:15, Sean Christopherson wrote:
> Officially "reward" David with guest_memfd responsibilities and authority,
> as he's been instrumental in pushing guest_memfd forward, and his ongoing
> input and feedback, especially from an mm/ perspective, is and will be
> critical to keeping us virtualization folks from going too far off the
> rails.
Thanks for the kind words, Sean!
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
>
> Cc: David Hildenbrand <david@kernel.org>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9eceeb6f699d..8dd5cdbef66f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14399,6 +14399,7 @@ F: drivers/video/backlight/ktz8866.c
> KVM GUEST_MEMFD
> M: Sean Christopherson <seanjc@google.com>
> M: Paolo Bonzini <pbonzini@redhat.com>
> +R: David Hildenbrand <david@kernel.org>
> L: kvm@vger.kernel.org
> S: Supported
> T: git git://git.kernel.org/pub/scm/virt/kvm/kvm.git
--
Cheers,
David
next prev parent reply other threads:[~2026-04-28 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 17:15 [RFC PATCH 0/5] MAINTAINERS: KVM tweaks and additions Sean Christopherson
2026-04-28 17:15 ` [RFC PATCH 1/5] MAINTAINERS: Add kvm-x86 tree to KVM x86 entries Sean Christopherson
2026-04-28 17:15 ` [RFC PATCH 2/5] KVM: guest_memfd: Move gmem function declarations to dedicated guest_memfd.h Sean Christopherson
2026-04-28 19:26 ` David Hildenbrand (Arm)
2026-04-30 19:07 ` Ackerley Tng
2026-04-30 21:38 ` Sean Christopherson
2026-04-28 17:15 ` [RFC PATCH 3/5] MAINTAINERS: Add an entry for KVM's guest_memfd Sean Christopherson
2026-04-28 19:27 ` David Hildenbrand (Arm)
2026-04-30 19:08 ` Ackerley Tng
2026-04-30 21:33 ` Sean Christopherson
2026-04-28 17:15 ` [RFC PATCH 4/5] MAINTAINERS: Add David H. as a KVM guest_memfd reviewer Sean Christopherson
2026-04-28 19:27 ` David Hildenbrand (Arm) [this message]
2026-04-30 19:08 ` Ackerley Tng
2026-04-28 17:15 ` [RFC PATCH 5/5] MAINTAINERS: Add myself (Sean) as a reviewer in the main KVM entry Sean Christopherson
2026-04-28 19:30 ` David Hildenbrand (Arm)
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=d6a90fc2-baf8-47a9-bda8-c21e55523677@kernel.org \
--to=david@kernel.org \
--cc=anup@brainfault.org \
--cc=borntraeger@linux.ibm.com \
--cc=chenhuacai@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maobibo@loongson.cn \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yosry@kernel.org \
--cc=zhaotianrui@loongson.cn \
/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