public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 4/7] doc/shell-test-api.txt
Date: Fri, 16 Dec 2022 10:49:15 +0100	[thread overview]
Message-ID: <Y5w/G2UiR/x6phkQ@pevik> (raw)
In-Reply-To: <1671166923-2173-4-git-send-email-xuyang2018.jy@fujitsu.com>

Hi Xu,

> Update tst_kvcmp usage.

> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
> ---
>  doc/shell-test-api.txt | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)

> diff --git a/doc/shell-test-api.txt b/doc/shell-test-api.txt
> index 73c9eff91..f35561e54 100644
> --- a/doc/shell-test-api.txt
> +++ b/doc/shell-test-api.txt
> @@ -652,13 +652,15 @@ tst_kvcmp
>  +++++++++

>  This command compares the currently running kernel version given conditions
> -with syntax similar to the shell test command.
> +with syntax similar to the shell test command. Now, the oldest supported kernel
> +version for ltp is 3.0, so we don't need this if comparing with very old version
               ^ upper case please (LTP)
> +ie 2.6.8 .
           ^ please remove this space.

I'm not a native speaker, but

with syntax similar to the shell test command. The oldest supported kernel
version for LTP is 3.0, therefore we don't need this if comparing with very old version
e.g. 2.6.8.

But is it really needed? Nobody will add these check nowadays.
Instead this I sent a patch to add this to doc/supported-kernel-libc-versions.txt
https://patchwork.ozlabs.org/project/ltp/patch/20221216094611.2924-2-pvorel@suse.cz/
(I also pinged few people + automated-testing@lists.yoctoproject.org in the
patchset to get some audience for minimal version - maybe we could raise higher.)

>  [source,sh]
>  -------------------------------------------------------------------------------
> -# Exit the test if kernel version is older or equal to 2.6.8
> -if tst_kvcmp -le 2.6.8; then
> -	tst_brk TCONF "Kernel newer than 2.6.8 is needed"
> +# Exit the test if kernel version is older or equal to 4.0.0
> +if tst_kvcmp -le 4.0.0; then
> +	tst_brk TCONF "Kernel newer than 4.0.0 is needed"
>  fi

Updating example is obviously correct.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
for this part only.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-12-16  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  5:01 [LTP] [PATCH v3 1/7] lib/tst_kvercmp: Remove old distnames Yang Xu
2022-12-16  5:01 ` [LTP] [PATCH v3 2/7] shell: Remove old kernel version check Yang Xu
2022-12-16  8:55   ` Petr Vorel
2022-12-16  5:01 ` [LTP] [PATCH v3 3/7] cgroup_regression_test.sh: Remove obselte test_6 Yang Xu
2022-12-16  9:02   ` Petr Vorel
2022-12-16  9:11     ` xuyang2018.jy
2022-12-16 10:36       ` Petr Vorel
2022-12-16  5:02 ` [LTP] [PATCH v3 4/7] doc/shell-test-api.txt Yang Xu
2022-12-16  9:49   ` Petr Vorel [this message]
2022-12-16  5:02 ` [LTP] [PATCH v3 5/7] Remove old kernel version check in C case when using tst_kvercmp Yang Xu
2022-12-16 10:03   ` Petr Vorel
2022-12-16  5:02 ` [LTP] [PATCH v3 6/7] Remove old kernel version check when using min_kver Yang Xu
2022-12-16 10:11   ` Petr Vorel
2022-12-16  5:02 ` [LTP] [PATCH v3 7/7] doc/c-test-api.txt Yang Xu
2022-12-16 10:12   ` Petr Vorel
2022-12-19  3:01     ` xuyang2018.jy
2022-12-19  7:38       ` Petr Vorel
2023-01-03 17:53       ` Petr Vorel

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=Y5w/G2UiR/x6phkQ@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=xuyang2018.jy@fujitsu.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