All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: kvmarm@lists.linux.dev, Marc Zyngier <maz@kernel.org>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: Include documentation in KVM/arm64 entry
Date: Sat, 29 Jun 2024 02:13:48 +0000	[thread overview]
Message-ID: <Zn9t3N4CxcqblFYO@linux.dev> (raw)
In-Reply-To: <63685fc4-38fb-f938-959d-2c1f96cff6b1@huawei.com>

On Sat, Jun 29, 2024 at 09:32:53AM +0800, Zenghui Yu wrote:
> On 2024/6/29 6:21, Oliver Upton wrote:
> > Ensure updates to the KVM/arm64 documentation get sent to the right
> > place.
> > 
> > Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
> > ---
> >  MAINTAINERS | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index aacccb376c28..05d71b852857 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -12078,6 +12078,7 @@ L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> >  L:	kvmarm@lists.linux.dev
> >  S:	Maintained
> >  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git
> > +F:	Documentation/virt/kvm/arm/
> >  F:	arch/arm64/include/asm/kvm*
> >  F:	arch/arm64/include/uapi/asm/kvm*
> >  F:	arch/arm64/kvm/
> 
> Should we include the vgic documentation (in
> Documentation/virt/kvm/devices/) as well? They're indeed KVM/arm64
> stuff.

Heh, yet another fine example for why I shouldn't send patches on a
Friday evening :)

Yes, we'll want to fold those in too, thanks for spotting this.

-- 
Thanks,
Oliver

  reply	other threads:[~2024-06-29  2:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 22:21 [PATCH] MAINTAINERS: Include documentation in KVM/arm64 entry Oliver Upton
2024-06-29  1:32 ` Zenghui Yu
2024-06-29  2:13   ` Oliver Upton [this message]
2024-06-29  2:24     ` Zenghui Yu
2024-07-03 23:25 ` 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=Zn9t3N4CxcqblFYO@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=pbonzini@redhat.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 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.