From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add KVM selftests to existing KVM entry
Date: Fri, 15 Mar 2019 11:40:50 -0700 [thread overview]
Message-ID: <20190315184050.GE11324@linux.intel.com> (raw)
In-Reply-To: <3bbaa29f-e70d-45a7-b93e-24ecc006bcb7@redhat.com>
On Fri, Mar 15, 2019 at 07:07:45PM +0100, Paolo Bonzini wrote:
> On 13/03/19 21:16, Sean Christopherson wrote:
> > Gah, this also needs: tools/testing/selftests/kvm/*/
> >
>
> No, it doesn't.
>
> $ scripts/get_maintainer.pl tools/testing/selftests/kvm/x86_64/state_test.c
> Paolo Bonzini <pbonzini@redhat.com> (supporter:KERNEL VIRTUAL MACHINE (KVM),commit_signer:8/9=89%,authored:3/9=33%)
> "Radim Krčmář" <rkrcmar@redhat.com> (supporter:KERNEL VIRTUAL MACHINE (KVM),commit_signer:1/9=11%)
Ah, I always run with --pattern-depth=1 when sending KVM patches to avoid
picking up the x86 maintainers. I guess now is as good a time as any to
dynamically select the depth.
That means the similiar "F: arch/x86/kvm/*/" entry I added is also
gratutious. Want me to send a revert for c2a7fad5fcd3 ("MAINTAINERS:
Add arch/x86/kvm sub-directories to existing KVM/x86 entry"), or just
leave it be?
> Queued, thanks.
>
> Paolo
prev parent reply other threads:[~2019-03-15 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 19:55 [PATCH] MAINTAINERS: Add KVM selftests to existing KVM entry Sean Christopherson
2019-03-13 20:16 ` Sean Christopherson
2019-03-15 18:07 ` Paolo Bonzini
2019-03-15 18:40 ` Sean Christopherson [this message]
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=20190315184050.GE11324@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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.