From: pratmal@google.com
To: david@kernel.org
Cc: akpm@linux-foundation.org, shuah@kernel.org,
yosryahmed@google.com, ljs@kernel.org, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] selftests/mm: use pattern matching in .gitignore
Date: Wed, 22 Apr 2026 19:08:47 +0000 [thread overview]
Message-ID: <20260422190847.216343-1-pratmal@google.com> (raw)
In-Reply-To: <03a23a7a-58fe-42f4-a294-9d688ce33e2d@kernel.org>
(Resending to correct David's email address. Apologies for the noise!)
On 4/22/26 18:04, David Hildenbrand (Arm) wrote:
> On 4/21/26 20:30, pratmal@google.com wrote:
>> From: Pratyush Mallick <pratmal@google.com>
>>
>> The current .gitignore hardcodes each generated test binary by name,
>> requiring updates every time a new test is added.
>>
>> Switch to the patten-matching approach similar to KVM:selftests.
>> Ignore everything by default and then allow source extensions (.c, .h, .sh)
>> and tracked non-source files.
> That looks pretty nice. Any reason for the RFC? (iow, are you unsure about some
> side-effects?)
Exactly that. I verified that the build works fine, however I sent it
as an RFC just to be cautious. I wanted to get some feedback in case this
might introduce some unwanted behavior that I'm not aware of. :)
Thanks,
Pratyush
prev parent reply other threads:[~2026-04-22 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 18:30 pratmal
2026-04-22 18:04 ` David Hildenbrand (Arm)
2026-04-22 19:01 ` pratmal
2026-04-22 19:08 ` pratmal [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=20260422190847.216343-1-pratmal@google.com \
--to=pratmal@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=yosryahmed@google.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