From: Sean Christopherson <seanjc@google.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust entry after renaming the vmx hyperv files
Date: Wed, 7 Dec 2022 21:25:36 +0000 [thread overview]
Message-ID: <Y5EE0MOaLGZUqa38@google.com> (raw)
In-Reply-To: <87pmcydyp0.fsf@redhat.com>
On Mon, Dec 05, 2022, Vitaly Kuznetsov wrote:
> Lukas Bulwahn <lukas.bulwahn@gmail.com> writes:
>
> > Commit a789aeba4196 ("KVM: VMX: Rename "vmx/evmcs.{ch}" to
> > "vmx/hyperv.{ch}"") renames the VMX specific Hyper-V files, but does not
> > adjust the entry in MAINTAINERS.
> >
> > Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> > broken reference.
> >
> > Repair this file reference in KVM X86 HYPER-V (KVM/hyper-v).
> >
>
> Fixes: a789aeba4196 ("KVM: VMX: Rename "vmx/evmcs.{ch}" to "vmx/hyperv.{ch}"")
>
> maybe?
Ya.
>
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > ---
> > MAINTAINERS | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ceda8a0abffa..8fda3844b55b 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -11457,7 +11457,7 @@ F: arch/x86/kvm/hyperv.*
> > F: arch/x86/kvm/kvm_onhyperv.*
> > F: arch/x86/kvm/svm/hyperv.*
> > F: arch/x86/kvm/svm/svm_onhyperv.*
> > -F: arch/x86/kvm/vmx/evmcs.*
> > +F: arch/x86/kvm/vmx/hyperv.*
> >
> > KVM X86 Xen (KVM/Xen)
> > M: David Woodhouse <dwmw2@infradead.org>
>
> Reviewed-by:
Since Vitaly left you hanging :-)
Reviewed-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2022-12-07 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:20 [PATCH] MAINTAINERS: adjust entry after renaming the vmx hyperv files Lukas Bulwahn
2022-12-05 8:47 ` Vitaly Kuznetsov
2022-12-07 21:25 ` 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=Y5EE0MOaLGZUqa38@google.com \
--to=seanjc@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=pbonzini@redhat.com \
--cc=vkuznets@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox