mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Borislav Petkov <bp@alien8.de>, Kiryl Shutsemau <kas@kernel.org>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Biju Das <biju.das.jz@bp.renesas.com>,
	 "biju.das.au" <biju.das.au@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Greg Kroah-Hartman	 <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	 "linux-kernel@vger.kernel.org"	 <linux-kernel@vger.kernel.org>,
	"linux-serial@vger.kernel.org"	 <linux-serial@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"	
	<linux-renesas-soc@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	 "linux-coco@lists.linux.dev"	 <linux-coco@lists.linux.dev>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	 Au Dang <au.dang.jx@renesas.com>
Subject: Re: [PATCH -v2] MAINTAINERS: Fix Intel TDX kernel file patterns
Date: Sat, 31 Oct 2026 09:43:44 -0700	[thread overview]
Message-ID: <35ba539820e1782bde038df98d3b49295eb7cd3a.camel@perches.com> (raw)
In-Reply-To: <20261031030112.GHauVZ-OI2KjdkjrcY@fat_crate.local>

On Fri, 2026-10-30 at 20:01 -0700, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> 
> A K: is a content regex file pattern which matches any text in a patch
> so if a commit message contains "tdx" as in
> 
>   has_tdxe_auto_clear
> 
> for example, see
> 
>   https://lore.kernel.org/r/20261026-g2ul_sci-v3-3-b3097163edd5@bp.renesas.com
> 
> get_maintainer.pl erroneously adds the x86 gang to the Cc list for what
> obviously is a completely unrelated patch.

It's not an error in get_maintainer.pl
and V2: no changelog


> So switch the x86 TDX patterns to files and directories (F:) wildcard
> type patterns and group them by path, for less false positives.
> 
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Link: https://lore.kernel.org/r/20261027055750.GBauA9XlPykc1c1Xhv@fat_crate.local

nack.  Bad file pattern below


> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -30347,8 +30347,11 @@ L:	linux-coco@lists.linux.dev
>  L:	kvm@vger.kernel.org
>  S:	Supported
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/tdx
> -N:	tdx
> -K:	\b(tdx)
> +F:	arch/x86/**/*tdx*
> +F:	Documentation/**/*tdx*
> +F:	drivers/virt/coco/tdx*/
> +F:	include/uapi/linux/tdx

No file match.  Probably should be:

F:	include/uapi/linux/tdx*

but as far as I can see there's only a single file there.

F:	include/uapi/linux/tdx-guest.h

> +F:	tools/testing/selftests/tdx/
>  
>  X86 VDSO
>  M:	Andy Lutomirski <luto@kernel.org>
> -- 
> 2.53.0
> 

  reply	other threads:[~2026-10-31 16:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 11:23 [PATCH v3 0/4] Fix transmit handling on SCI/RSCI ports Biju Das
2026-10-26 11:23 ` [PATCH v3 1/4] serial: sh-sci: Drop TE disable at end of transmission on SCI Biju Das
2026-10-26 11:23 ` [PATCH v3 2/4] serial: sh-sci: Keep TX enabled on TEI while data is pending Biju Das
2026-10-26 11:23 ` [PATCH v3 3/4] serial: sh-sci: Skip TDxE clear when hardware clears it automatically Biju Das
2026-10-26 11:23 ` [PATCH v3 4/4] serial: sh-sci: Toggle TE when restoring SCSCR in console write on SCI Biju Das
2026-10-27  5:57 ` [PATCH v3 0/4] Fix transmit handling on SCI/RSCI ports Borislav Petkov
2026-10-27  7:19   ` Biju Das
2026-10-27  7:23     ` Krzysztof Kozlowski
2026-10-27  8:33       ` Biju Das
2026-10-27  9:34         ` Krzysztof Kozlowski
2026-10-27 20:54           ` Borislav Petkov
2026-10-28  9:13             ` Biju Das
2026-10-28 11:02             ` Krzysztof Kozlowski
2026-10-28 15:47               ` Borislav Petkov
2026-10-30  2:33                 ` [PATCH] MAINTAINERS: Fix Intel TDX kernel file patterns Borislav Petkov
2026-10-30 14:17                   ` Dave Hansen
2026-10-30 14:40                   ` Kiryl Shutsemau
2026-10-30 18:22                     ` Borislav Petkov
2026-10-30 17:16                   ` Joe Perches
2026-10-30 18:20                     ` Borislav Petkov
2026-10-30 19:40                       ` Joe Perches
2026-10-30 19:49                         ` Borislav Petkov
2026-10-31  3:01                   ` [PATCH -v2] " Borislav Petkov
2026-10-31 16:43                     ` Joe Perches [this message]
2026-10-31 20:27                       ` Borislav Petkov
2026-10-31 22:52                         ` Joe Perches
2026-10-31 23:59                           ` Borislav Petkov
2026-11-01  0:38                             ` Joe Perches
2026-11-01  1:47                               ` Borislav Petkov
2026-11-01  5:35                                 ` Joe Perches

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=35ba539820e1782bde038df98d3b49295eb7cd3a.camel@perches.com \
    --to=joe@perches.com \
    --cc=au.dang.jx@renesas.com \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=kas@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=x86@kernel.org \
    /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

all inboxes | Powered by JetHome®