From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Khaled Elnaggar" <khaledelnaggarlinux@gmail.com>,
<shuah@kernel.org>, <peterhuewe@gmx.de>, <jgg@ziepe.ca>
Cc: <linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-integrity@vger.kernel.org>
Subject: Re: [PATCH v4] selftests: tpm2: create a dedicated .gitignore
Date: Mon, 27 Jan 2025 19:18:09 +0200 [thread overview]
Message-ID: <D7D0Z3L6SBSF.1MSDA2G2MV3QZ@kernel.org> (raw)
In-Reply-To: <20250126195147.902608-1-khaledelnaggarlinux@gmail.com>
On Sun Jan 26, 2025 at 9:51 PM EET, Khaled Elnaggar wrote:
> The tpm2 selftests produce two logs: SpaceTest.log and
> AsyncTest.log. Only SpaceTest.log was listed in selftests/.gitignore,
> while AsyncTest.log remained untracked.
>
> This change creates a dedicated .gitignore in the tpm2/ directory to
> manage these entries, keeping tpm2-specific patterns isolated from
> parent .gitignore.
>
> Signed-off-by: Khaled Elnaggar <khaledelnaggarlinux@gmail.com>
> ---
> Oh no, I realized there was a mistake in v3. I wrote tpm2/*.log in the
> tpm2/.gitignore file, which is unnecessary since tpm2/.gitignore is
> already scoped to the tpm2 directory.
> All entries are automatically relative to the tpm2 directory.
>
> I’ve fixed it by removing the redundant tpm2/ prefix from the entries
> in tpm2/.gitignore.
>
> Apologies for not catching this earlier, I tested it after submitting
> the patch because I was confident v2 was correct, but the issue was
> introduced in v3.
>
> Thanks,
> Khaled
>
> Changes:
> v4: Correct the mistake in v3
> v3: Improve commit message (and introduce a mistake)
> v2: Created a dedicated .gitignore
> v1: https://lore.kernel.org/linux-kselftest/20250116085929.313677-1-eng.khaled.elnaggar@gmail.com
> ---
> tools/testing/selftests/.gitignore | 1 -
> tools/testing/selftests/tpm2/.gitignore | 4 ++++
> 2 files changed, 4 insertions(+), 1 deletion(-)
> create mode 100644 tools/testing/selftests/tpm2/.gitignore
>
> diff --git a/tools/testing/selftests/.gitignore b/tools/testing/selftests/.gitignore
> index cb24124ac5b9..674aaa02e396 100644
> --- a/tools/testing/selftests/.gitignore
> +++ b/tools/testing/selftests/.gitignore
> @@ -4,7 +4,6 @@ gpiogpio-hammer
> gpioinclude/
> gpiolsgpio
> kselftest_install/
> -tpm2/SpaceTest.log
>
> # Python bytecode and cache
> __pycache__/
> diff --git a/tools/testing/selftests/tpm2/.gitignore b/tools/testing/selftests/tpm2/.gitignore
> new file mode 100644
> index 000000000000..910bbdbb336a
> --- /dev/null
> +++ b/tools/testing/selftests/tpm2/.gitignore
> @@ -0,0 +1,4 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +AsyncTest.log
> +SpaceTest.log
> +
> --
> 2.45.2
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
prev parent reply other threads:[~2025-01-27 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 6:50 [PATCH v2] selftests: tpm2: create a dedicated .gitignore Khaled Elnaggar
2025-01-23 9:47 ` Jarkko Sakkinen
2025-01-24 14:35 ` Khaled Elnaggar
2025-01-24 16:37 ` Jarkko Sakkinen
2025-01-24 16:42 ` Jarkko Sakkinen
2025-01-25 8:58 ` Khaled Elnaggar
2025-01-25 19:20 ` Jarkko Sakkinen
2025-01-26 10:50 ` Khaled Elnaggar
2025-01-26 14:22 ` [PATCH v3] " Khaled Elnaggar
2025-01-26 16:30 ` Jarkko Sakkinen
2025-01-26 19:51 ` [PATCH v4] " Khaled Elnaggar
2025-01-27 17:18 ` Jarkko Sakkinen [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=D7D0Z3L6SBSF.1MSDA2G2MV3QZ@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=khaledelnaggarlinux@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.