From: Joe Perches <joe@perches.com>
To: Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Kiryl Shutsemau <kas@kernel.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
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: Sun, 01 Nov 2026 11:54:42 -0800 [thread overview]
Message-ID: <874236faffbe90543d69361f04628fd8047ab1b8.camel@perches.com> (raw)
In-Reply-To: <20261101193759.GBaueVF-1a0H8BDmZ2@fat_crate.local>
On Sun, 2026-11-01 at 11:37 -0800, Borislav Petkov wrote:
> On Sun, Nov 01, 2026 at 10:59:24AM -0800, Joe Perches wrote:
> > Not completely no.
>
> Well, whatever you do, this needs some documentation so that it is perfectly
> clear to people using patterns.
>
> Something perhaps like this below. You probably can come up with a better
> formulation - my only angle is to make this as easier and as clear to users of
> the pattern stuff as possible.
Thanks.
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -30,13 +30,16 @@ Descriptions of section entries and preferred order
> See Documentation/maintainer/maintainer-entry-profile.rst for details.
> T: *SCM* tree type and location.
> Type is one of: git, hg, quilt, stgit, topgit
> - F: *Files* and directories wildcard patterns.
> + F: *Files* and directories wildcard patterns. The matching strategy
> + mimicks git's pathspec shell glob patterns with some exceptions.
> A trailing slash includes all files and subdirectory files.
> F: drivers/net/ all files in and below drivers/net
> F: drivers/net/* all files in drivers/net, but not below
> F: */net/* all files in "any top level directory"/net
> F: fs/**/*foo*.c all *foo*.c files in any subdirectory of fs
> - One pattern per line. Multiple F: lines acceptable.
> + One pattern per line. Multiple F: lines acceptable. One way to
> + verify the pattern is using something like
> + git ls-files -- <pattern>
Clarity is good.
Perhaps <pattern> needs to be '<pattern>' to avoid
command-line expansion.
I do think it was already generally understood though as
there was just one exception to the pattern match style
in the existing more than ten thousand ^[FX]: MAINTAINER
entries.
next prev parent reply other threads:[~2026-11-01 19:54 UTC|newest]
Thread overview: 35+ 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
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
2026-11-01 18:54 ` Borislav Petkov
2026-11-01 18:59 ` Joe Perches
2026-11-01 19:37 ` Borislav Petkov
2026-11-01 19:54 ` Joe Perches [this message]
2026-11-01 20:17 ` Borislav Petkov
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=874236faffbe90543d69361f04628fd8047ab1b8.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--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®