lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190315184050.GE11324@linux.intel.com>
Date:   Fri, 15 Mar 2019 11:40:50 -0700
From:   Sean Christopherson <sean.j.christopherson@...el.com>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     Radim Krčmář <rkrcmar@...hat.com>,
        kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add KVM selftests to existing KVM entry

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@...hat.com> (supporter:KERNEL VIRTUAL MACHINE (KVM),commit_signer:8/9=89%,authored:3/9=33%)
> "Radim Krčmář" <rkrcmar@...hat.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ