public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Li Zhijian <lizhijian@fujitsu.com>,
	linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Cc: linux-kernel@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 3/3] selftests: ignore output files and clean them in Makefile
Date: Tue, 15 Oct 2024 09:56:29 -0600	[thread overview]
Message-ID: <6dfa4266-bbe7-4c30-a3ee-1ff5a4b28221@linuxfoundation.org> (raw)
In-Reply-To: <20241015010817.453539-3-lizhijian@fujitsu.com>

On 10/14/24 19:08, Li Zhijian wrote:
> After `make run_tests`, the git status complains:
> Untracked files:
>      (use "git add <file>..." to include in what will be committed)
>          cpufreq/cpufreq_selftest.dmesg_cpufreq.txt
>          cpufreq/cpufreq_selftest.dmesg_full.txt
>          cpufreq/cpufreq_selftest.txt
>          zram/err.log
> 
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> ---
>   tools/testing/selftests/cpufreq/.gitignore | 1 +
>   tools/testing/selftests/cpufreq/Makefile   | 1 +
>   tools/testing/selftests/zram/.gitignore    | 1 +

Same comment here - two separate patches and include
key people to the email recipients.

>   3 files changed, 3 insertions(+)
>   create mode 100644 tools/testing/selftests/cpufreq/.gitignore
>   create mode 100644 tools/testing/selftests/zram/.gitignore
> 
> diff --git a/tools/testing/selftests/cpufreq/.gitignore b/tools/testing/selftests/cpufreq/.gitignore
> new file mode 100644
> index 000000000000..f684d27f5d91
> --- /dev/null
> +++ b/tools/testing/selftests/cpufreq/.gitignore
> @@ -0,0 +1 @@
> +cpufreq_selftest.*
> diff --git a/tools/testing/selftests/cpufreq/Makefile b/tools/testing/selftests/cpufreq/Makefile
> index c86ca8342222..9b2ccb10b0cf 100644
> --- a/tools/testing/selftests/cpufreq/Makefile
> +++ b/tools/testing/selftests/cpufreq/Makefile
> @@ -3,6 +3,7 @@ all:
>   
>   TEST_PROGS := main.sh
>   TEST_FILES := cpu.sh cpufreq.sh governor.sh module.sh special-tests.sh
> +EXTRA_CLEAN := cpufreq_selftest.dmesg_cpufreq.txt cpufreq_selftest.dmesg_full.txt cpufreq_selftest.txt
>   
>   include ../lib.mk
>   
> diff --git a/tools/testing/selftests/zram/.gitignore b/tools/testing/selftests/zram/.gitignore
> new file mode 100644
> index 000000000000..b4a2cb6fafa6
> --- /dev/null
> +++ b/tools/testing/selftests/zram/.gitignore
> @@ -0,0 +1 @@
> +err.log

thanks,
-- Shuah

  reply	other threads:[~2024-10-15 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15  1:08 [PATCH 1/3] selftests: Add a few missing gitignore files Li Zhijian
2024-10-15  1:08 ` [PATCH 2/3] selftests/net: Fix ./ns-XXXXXX not cleanup Li Zhijian
2024-10-15 15:43   ` Jakub Kicinski
2024-10-15  1:08 ` [PATCH 3/3] selftests: ignore output files and clean them in Makefile Li Zhijian
2024-10-15 15:56   ` Shuah Khan [this message]
2024-10-15 15:38 ` [PATCH 1/3] selftests: Add a few missing gitignore files Shuah Khan
2024-10-16  0:42   ` Zhijian Li (Fujitsu)
2024-10-17 20:22 ` kernel test robot

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=6dfa4266-bbe7-4c30-a3ee-1ff5a4b28221@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lizhijian@fujitsu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox