From: Avinesh Kumar <akumar@suse.de>
To: Souta Kawahara <souta.kawahara@miraclelinux.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1 1/1] doc/c-test-api.txt: fix wrong chapter number
Date: Thu, 24 Aug 2023 12:25:10 +0530 [thread overview]
Message-ID: <2424913.C0n9F0bVQ2@localhost> (raw)
In-Reply-To: <447b0209996f33c5d7f6f5e0f146ca1abfe28346.1692858827.git.souta.kawahara@miraclelinux.com>
Hi Souta,
Reviewed-by: Avinesh Kumar <akumar@suse.de>
On Thursday, August 24, 2023 12:06:22 PM IST Souta Kawahara wrote:
> Chapter number "1.36" was duplicated.
> Incremented the second "1.36" and subsequent chapters.
>
> Signed-off-by: Souta Kawahara <souta.kawahara@miraclelinux.com>
> ---
> doc/c-test-api.txt | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/doc/c-test-api.txt b/doc/c-test-api.txt
> index e4e88edec..3c059bb3a 100644
> --- a/doc/c-test-api.txt
> +++ b/doc/c-test-api.txt
> @@ -2141,7 +2141,7 @@ the prefix field of file pointed by path equals to the
> value passed to this func Also having a similar api pair
> TST_ASSERT_FILE_INT/STR(path, prefix, val) to assert the field value of
> file.
>
> -1.36 Using Control Group
> +1.37 Using Control Group
> ~~~~~~~~~~~~~~~~~~~~~~~~
>
> Some LTP tests need specific Control Group configurations. 'tst_cgroup.h'
> @@ -2322,19 +2322,19 @@ kernel docs. Presently the LTP library does not
> attempt to handle most differences in semantics. It does the minimal amount
> of work to make testing on both V1 and V2 feasible.
>
> -1.37 Require minimum numbers of CPU for a testcase
> +1.38 Require minimum numbers of CPU for a testcase
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Some tests require more than specific number of CPU. It can be defined with
> `.min_cpus = N`.
>
> -1.38 Require minimum size of MemAvailable for a testcase
> +1.39 Require minimum size of MemAvailable for a testcase
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Some tests require more than specific size(MB) of MemAvailable. It can be
> defined with `.min_mem_avail = N`.
>
> -1.39 Test tags
> +1.40 Test tags
> ~~~~~~~~~~~~~~
>
> Test tags are name-value pairs that can hold any test metadata.
> @@ -2376,7 +2376,7 @@ struct tst_test test = {
> };
> ---------------------------------------------------------------------------
> ----
>
> -1.40 Testing on the specific architecture
> +1.41 Testing on the specific architecture
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Testcases for specific arch should be limited on that only being supported
> platform to run, we now involve a '.supported_archs' to achieve this
> feature @@ -2412,7 +2412,7 @@ static struct tst_test test = {
> };
> ---------------------------------------------------------------------------
> ----
>
> -1.41 Skipping test based on system state
> +1.42 Skipping test based on system state
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Test can be skipped on various conditions: on enabled SecureBoot
> ('.skip_in_secureboot = 1'), lockdown ('.skip_in_lockdown = 1') or in
> 32-bit
--
Regards,
Avinesh
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-08-24 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 6:36 [LTP] [PATCH v1 1/1] doc/c-test-api.txt: fix wrong chapter number Souta Kawahara
2023-08-24 6:55 ` Avinesh Kumar [this message]
2023-08-25 9:05 ` Li Wang
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=2424913.C0n9F0bVQ2@localhost \
--to=akumar@suse.de \
--cc=ltp@lists.linux.it \
--cc=souta.kawahara@miraclelinux.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