Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 3/7] lib: Add support for max_kver to struct tst_test and tst_fs
Date: Wed, 12 Aug 2026 15:11:12 +0200	[thread overview]
Message-ID: <20260812131112.GC1758016@pevik> (raw)
In-Reply-To: <anxo4jwILKGq_H8J@yuki.lan>

> Hi!
> > I deliberately did not add it and documented my intention in
> > doc/developers/writing_tests.rst LTP C And Shell Test API Comparison table
> > +    * - .max_kver
> > +      - not implemented

> This is correct since this is different shell API (v2). The change I
> requested is newest shell API (v3).

Unfortunately we have many tests in v2, I hoped we would at lest mention there
is v2. I'm not happy with the fact that we document only v3, IMHO at least have
link v2 API is in doc/old/Shell-.... would be good.

> This is also reason why I asked for deletion of this table, it
> documments older API (tst_test.sh) and confuses people.

BTW the test was moved there in 4a72aada873, which was 4 months ago before you
wrote shell loader API (5528da0231).

I still think it's useful (until we rewrite more tests into shell API => now we
have many tests for which we delete documentation), but it should be clearly
visible it's for tst_test.sh (v2 API). But I'm ok to remove it if you don't want
to waste time with v2 (we removed part of old docs in 4a72aada873 which removed
also doc/old/Test-Writing-Guidelines.asciidoc which had this table).

Kind regards,
Petr

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

  reply	other threads:[~2026-08-12 13:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 16:00 [LTP] [PATCH v5 0/7] Add support for .max_kver Petr Vorel
2026-08-10 16:00 ` [LTP] [PATCH v5 1/7] tst_kvercmp: Factor out error handling Petr Vorel
2026-08-10 16:57   ` [LTP] " linuxtestproject.agent
2026-08-10 17:03     ` Petr Vorel
2026-08-11  7:01   ` [LTP] [PATCH v5 1/7] " Andrea Cervesato via ltp
2026-08-12 10:50   ` Cyril Hrubis
2026-08-10 16:00 ` [LTP] [PATCH v5 2/7] lib: Rename function check_kver() => check_min_kver() Petr Vorel
2026-08-10 16:00 ` [LTP] [PATCH v5 3/7] lib: Add support for max_kver to struct tst_test and tst_fs Petr Vorel
2026-08-11  7:04   ` Andrea Cervesato via ltp
2026-08-12 11:05   ` Cyril Hrubis
2026-08-12 12:30     ` Petr Vorel
2026-08-12 12:36       ` Cyril Hrubis
2026-08-12 13:11         ` Petr Vorel [this message]
2026-08-12 12:44       ` Cyril Hrubis
2026-08-12 13:16         ` Petr Vorel
2026-08-12 11:06   ` Cyril Hrubis
2026-08-12 13:00     ` Petr Vorel
2026-08-10 16:00 ` [LTP] [PATCH v5 4/7] creat07: Avoid timeout on the test failure Petr Vorel
2026-08-11  7:04   ` Andrea Cervesato via ltp
2026-08-10 16:00 ` [LTP] [PATCH v5 5/7] creat07: execve04: Remove version check, add linux-git Petr Vorel
2026-08-10 16:00 ` [LTP] [PATCH v5 6/7] fanotify20: Skip on v7.2 Petr Vorel
2026-08-10 16:00 ` [LTP] [PATCH v5 7/7] lib: Add 2 basic tests for .min_kver && .max_kver Petr Vorel
2026-08-11  7:13   ` Andrea Cervesato via ltp
2026-08-11  8:49     ` Petr Vorel
2026-08-11  8:53       ` Andrea Cervesato via ltp
2026-08-11 10:10   ` Avinesh Kumar via ltp
2026-08-11  1:45 ` [LTP] [PATCH v5 0/7] Add support for .max_kver 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=20260812131112.GC1758016@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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