From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Shuah Khan <shuah@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/kselftest: add more guidelines for adding new tests
Date: Fri, 18 Mar 2022 11:50:34 +0700 [thread overview]
Message-ID: <07033c8a-fe1a-f97e-49b3-48d1da1e0413@gmail.com> (raw)
In-Reply-To: <20220317172758.582690-1-usama.anjum@collabora.com>
On 18/03/22 00.27, Muhammad Usama Anjum wrote:
> Add the following new guidelines:
> - Add instruction to use lib.mk
> - Add instruction about how to use headers from kernel source
> - Add instruction to add .gitignore file
> - Add instruction about how to add new test in selftests/Makefile
> - Add instruction about different build commands to test
>
Too verbose, because people can figure out what were added in the diff
without explicitly mention them.
> + * Use lib.mk instead of writing Makefile from sratch. Specify flags and
> + binaries generation flags on need basis before including lib.mk. ::
> +
> + CFLAGS = $(KHDR_INCLUDES)
> + TEST_GEN_PROGS := close_range_test
> + include ../lib.mk
> +
I think what you mean is "In your Makefile, use facilities from lib.mk by
including it instead of reinventing the wheel.", right?
> + * Add new test name in TARGETS in selftests/Makefile::
> +
> + TARGETS += android
> +
> + * All of the following build commands should be successful
> +
> + - Same directory build of kselftests::
> +
> + make kselftest-all
> + make kselftest-install
> + make kselftest-clean
> + make kselftest-gen_tar
> +
> + - Build with absolute output directory path::
> +
> + make kselftest-all O=/abs_build_path
> + make kselftest-install O=/abs_build_path
> + make kselftest-clean O=/abs_build_path
> + make kselftest-gen_tar O=/abs_build_path
> +
> + - Build with relative output directory path::
> +
> + make kselftest-all O=relative_path
> + make kselftest-install O=relative_path
> + make kselftest-clean O=relative_path
> + make kselftest-gen_tar O=relative_path
> +
> + - Build from Makefile of selftests directly::
> +
> + make -C tools/testing/selftests
> + make -C tools/testing/selftests O=/abs_build_path
> + make -C tools/testing/selftests O=relative_path
> +
For simplicity, we can say "All changes should pass
kselftest-{all,install,clean,gen_tar} builds."
You don't need to spell out full command-line in the guideline unless
absolutely necessary, in general.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-03-18 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 17:27 [PATCH] docs/kselftest: add more guidelines for adding new tests Muhammad Usama Anjum
2022-03-18 4:50 ` Bagas Sanjaya [this message]
2022-05-21 7:02 ` Muhammad Usama Anjum
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=07033c8a-fe1a-f97e-49b3-48d1da1e0413@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.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