Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
	Shuah Khan <shuah@kernel.org>, SeongJae Park <sj@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4 0/3] selftests: add missing gitignore files and include generated objects
Date: Tue, 20 Feb 2024 16:31:58 -0700	[thread overview]
Message-ID: <78dd68bd-d5ed-4549-870e-7514b300fdc5@linuxfoundation.org> (raw)
In-Reply-To: <20240214-selftest_gitignore-v4-0-857b39cef2fa@gmail.com>

On 2/13/24 17:03, Javier Carrasco wrote:
> This series aims to keep the git status clean after building the
> selftests by adding some missing .gitignore files and object inclusion
> in existing .gitignore files. This is one of the requirements listed in
> the selftests documentation for new tests, but it is not always followed
> as desired.
> 
> After adding these .gitignore files and including the generated objects,
> the working tree appears clean again.
> 
> To: Shuah Khan <shuah@kernel.org>
> To: SeongJae Park <sj@kernel.org>
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-kselftest@vger.kernel.org
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> 
> Changes in v4:
> - damon: remove from the series to apply it in mm separately.
> - Link to v3: https://lore.kernel.org/r/20240213-selftest_gitignore-v3-0-1f812368702b@gmail.com
> 
> Changes in v3:
> - General: base on mm-unstable to avoid conflicts.
> - damon: add missing Closes tag.
> - Link to v2: https://lore.kernel.org/r/20240212-selftest_gitignore-v2-0-75f0de50a178@gmail.com
> 
> Changes in v2:
> - Remove patch for netfilter (not relevant anymore).
> - Add patch for damon (missing binary in .gitignore).
> - Link to v1: https://lore.kernel.org/r/20240101-selftest_gitignore-v1-0-eb61b09adb05@gmail.com
> 
> ---
> Javier Carrasco (3):
>        selftests: uevent: add missing gitignore
>        selftests: thermal: intel: power_floor: add missing gitignore
>        selftests: thermal: intel: workload_hint: add missing gitignore
> 
>   tools/testing/selftests/thermal/intel/power_floor/.gitignore   | 1 +
>   tools/testing/selftests/thermal/intel/workload_hint/.gitignore | 1 +
>   tools/testing/selftests/uevent/.gitignore                      | 1 +
>   3 files changed, 3 insertions(+)
> ---
> base-commit: 7e90b5c295ec1e47c8ad865429f046970c549a66
> change-id: 20240101-selftest_gitignore-7da2c503766e
> 
> Best regards,


Applied to next for Linux 6.9-rc1

thanks,
-- Shuah


      parent reply	other threads:[~2024-02-20 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  0:03 [PATCH v4 0/3] selftests: add missing gitignore files and include generated objects Javier Carrasco
2024-02-14  0:03 ` [PATCH v4 1/3] selftests: uevent: add missing gitignore Javier Carrasco
2024-02-14  0:03 ` [PATCH v4 2/3] selftests: thermal: intel: power_floor: " Javier Carrasco
2024-02-14  0:03 ` [PATCH v4 3/3] selftests: thermal: intel: workload_hint: " Javier Carrasco
2024-02-20 23:31 ` Shuah Khan [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=78dd68bd-d5ed-4549-870e-7514b300fdc5@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=sj@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