[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97e322a3-0526-414d-a288-835d11ee2b1a@intel.com>
Date: Tue, 8 Jul 2025 08:17:16 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Paolo Bonzini <pbonzini@...hat.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Rick Edgecombe <rick.p.edgecombe@...el.com>,
Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev
Subject: Re: [PATCH 1/3] MAINTAINERS: Update the file list in the TDX entry.
On 7/8/25 07:24, Sean Christopherson wrote:
>> That file list is getting a bit long, but it _is_ the truth.
> What about adding
>
> K: tdx
>
> instead of listing each file individually? That might also help clarify what's
> up for cases where there is overlap, e.g. with KVM, to convey that this is a
> "secondary" entry of sorts.
Good idea. There are a couple of "tdx" things in the tree that aren't
TDX, but:
N: tdx
K: \b(tdx)
seems like it might be a _bit_ more precise. I don't see any filenames
with "tdx" in them that are false positives.
Powered by blists - more mailing lists