From: Will Deacon <will@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: maz@kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, seanjc@google.com, kvm@vger.kernel.org,
kvmarm@lists.linux.dev, james.morse@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Add Oliver Upton as co-maintainer of KVM/arm64
Date: Tue, 24 Jan 2023 09:37:29 +0000 [thread overview]
Message-ID: <20230124093728.GA26080@willie-the-truck> (raw)
In-Reply-To: <20230123210256.2728218-1-oliver.upton@linux.dev>
On Mon, Jan 23, 2023 at 09:02:56PM +0000, Oliver Upton wrote:
> Going forward I intend to help Marc with maintaining KVM/arm64. We've
> spoken about this quite a bit and he has been a tremendous help in
> ramping up to the task (thank you!). We haven't worked out the exact
> details of how the process will work, but the goal is to even out the
> maintenance responsibilities to give us both ample time for development.
>
> To that end, updating the maintainers entry to reflect the change.
>
> Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 42fc47c6edfd..7323efcc1270 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11355,9 +11355,9 @@ F: virt/kvm/*
>
> KERNEL VIRTUAL MACHINE FOR ARM64 (KVM/arm64)
> M: Marc Zyngier <maz@kernel.org>
> +M: Oliver Upton <oliver.upton@linux.dev>
Ya know, alphabetical order tends to put Mr Z at the bottom of the list,
but I can understand why you don't necessarily want to be first in the
pack just yet!
In any case, this is really great to see:
Acked-by: Will Deacon <will@kernel.org>
Thank you!
Will
next prev parent reply other threads:[~2023-01-24 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 21:02 Oliver Upton
2023-01-24 9:37 ` Will Deacon [this message]
2023-01-24 21:18 ` Oliver Upton
2023-01-24 9:51 ` Marc Zyngier
2023-01-30 19:13 ` Oliver Upton
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=20230124093728.GA26080@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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
all inboxes | Powered by JetHome®