From: Sarthak Sharma <sarthak.sharma@arm.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: add pkey_sighandler_tests to .gitignore
Date: Mon, 18 May 2026 10:36:11 +0530 [thread overview]
Message-ID: <62bb3ce0-5d09-4280-bb30-9f38b0fe6ae7@arm.com> (raw)
In-Reply-To: <agoPJHwC_3PnH1BQ@kernel.org>
Hi Mike!
On 5/18/26 12:25 AM, Mike Rapoport wrote:
> Hi Sarthak,
>
> On Fri, May 15, 2026 at 06:29:49PM +0530, Sarthak Sharma wrote:
>> .gitignore currently does not include the binary
>> pkey_sighandler_tests. Add it to .gitignore.
>>
>> Signed-off-by: Sarthak Sharma <sarthak.sharma@arm.com>
>> ---
>> tools/testing/selftests/mm/.gitignore | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/testing/selftests/mm/.gitignore b/tools/testing/selftests/mm/.gitignore
>> index b0c30c5ee9e3..1b1d9ed87039 100644
>> --- a/tools/testing/selftests/mm/.gitignore
>> +++ b/tools/testing/selftests/mm/.gitignore
>> @@ -62,3 +62,4 @@ merge
>> prctl_thp_disable
>> rmap
>> folio_split_race_test
>> +pkey_sighandler_tests
>
> There are patches that switch .gitignore to a pattern-matching approach:
>
> https://lore.kernel.org/all/20260511173411.267628-1-pratmal@google.com/
>
> With those there'd be no need to list every executable in .gitignore
> explicitly.
Thank you for letting me know. In that case, my patch may become
unnecessary once this series lands.
>
>> --
>> 2.39.5
>>
>
prev parent reply other threads:[~2026-05-18 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 12:59 Sarthak Sharma
2026-05-17 18:55 ` Mike Rapoport
2026-05-18 5:06 ` Sarthak Sharma [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=62bb3ce0-5d09-4280-bb30-9f38b0fe6ae7@arm.com \
--to=sarthak.sharma@arm.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@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®