From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 2/4] lib: Introduce LTP_KCONFIG_DISABLE environment variables
Date: Fri, 7 Jan 2022 02:00:36 +0000 [thread overview]
Message-ID: <61D79EEE.5030904@fujitsu.com> (raw)
In-Reply-To: <Ydb1vzPzp9R2g2kk@yuki>
Hi Cyril
> Hi!
>>>> diff --git a/doc/user-guide.txt b/doc/user-guide.txt
>>>> index 494652618..8d4435a28 100644
>>>> --- a/doc/user-guide.txt
>>>> +++ b/doc/user-guide.txt
>>>> @@ -18,6 +18,9 @@ For running LTP network tests see `testcases/network/README.md`.
>>>> | 'LTP_SINGLE_FS_TYPE' | Testing only - specifies filesystem instead all
>>>> supported (for tests with '.all_filesystems').
>>>> | 'LTP_DEV_FS_TYPE' | Filesystem used for testing (default: 'ext2').
>>>> +| 'LTP_KCONFIG_DISABLE' | Switch for kernel config check functionality.
>>>> + 'y' or '1': disable kconfig check,
>>>> + 'n' or '0': enable kconfig check.
>>
>>> Maybe it would be better named LTP_KCONFIG_SKIP or even
>>> KCONFIG_SKIP_CHECK we do have KCONFIG_PATH so it would make sense to
>>> keep the kernel config related variables prefixed with just KCONFIG_
>>
>>> I think that the point made by Tim Bird was that the KCONFIG_PATH should
>>> be standartized variable among testsuites, so it makes sense to have
>>> KCONFIG_SKIP_CHECK as a standartized variable as well.
>>
>> Is it too bad to have LTP_KCONFIG_SKIP_CHECK and LTP_KCONFIG_PATH ?
>> Maybe we could change it even now.
>
> Yes, the whole reason not to prefix it with LTP_ is to have a standard
> among all the testsuites. The more variables are standartized the
> better.
This make me remember xfstests testsuite also has KCONFIG_PATH
environment variable.
I will use KCONFIG_SKIP_CHECK name firstly, Unless Tim objects(may know
other testsuite has used KCONFIG_ environment variable ) or has a
better naming method.
Best Regards
Yang Xu
>
>> TST_NO_CLEANUP (IMHO should be changed to LTP_NO_CLEANUP).
>
> Unless we want to have a standard for that one as well. Really all we
> need to is to create a page with the description of these variables and
> agree on a common subset. It's that simple, but someone has to actually
> do it.
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-07 2:00 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 6:57 [LTP] [PATCH v1 1/3] lib/tst_kconfig: Modify the return type of tst_kconfig_check function Yang Xu
2022-01-04 6:57 ` [LTP] [PATCH v1 2/3] shell: add kconfig parse api Yang Xu
2022-01-04 11:04 ` Petr Vorel
2022-01-05 7:15 ` xuyang2018.jy
2022-01-05 14:34 ` Petr Vorel
2022-01-06 5:59 ` xuyang2018.jy
2022-01-06 8:16 ` xuyang2018.jy
2022-01-06 9:25 ` [LTP] [PATCH v2 1/4] lib/tst_kconfig: Modify the return type of tst_kconfig_check function Yang Xu
2022-01-06 9:25 ` [LTP] [PATCH v2 2/4] lib: Introduce LTP_KCONFIG_DISABLE environment variables Yang Xu
2022-01-06 9:49 ` Petr Vorel
2022-01-06 9:52 ` Petr Vorel
2022-01-06 11:07 ` Cyril Hrubis
2022-01-06 11:50 ` Petr Vorel
2022-01-06 13:59 ` Cyril Hrubis
2022-01-06 17:41 ` Petr Vorel
2022-01-07 2:00 ` xuyang2018.jy [this message]
2022-01-06 9:25 ` [LTP] [PATCH v2 3/4] shell: add kconfig parse api Yang Xu
2022-01-06 10:40 ` Petr Vorel
2022-01-06 11:19 ` Cyril Hrubis
2022-01-07 3:54 ` Li Wang
2022-01-07 4:08 ` xuyang2018.jy
2022-01-07 7:04 ` Li Wang
2022-01-07 8:28 ` xuyang2018.jy
2022-01-07 8:41 ` Li Wang
2022-01-07 9:46 ` Cyril Hrubis
2022-01-07 9:56 ` xuyang2018.jy
2022-01-07 9:05 ` Petr Vorel
2022-01-07 9:22 ` xuyang2018.jy
2022-01-07 12:07 ` Petr Vorel
2022-01-07 7:33 ` Petr Vorel
2022-01-06 9:25 ` [LTP] [PATCH v2 4/4] sysctl/sysctl02.sh: Use kconfig shell api Yang Xu
2022-01-06 11:20 ` Cyril Hrubis
2022-01-10 1:49 ` [LTP] [PATCH v3 1/4] lib/tst_kconfig: Modify the return type of tst_kconfig_check function Yang Xu
2022-01-10 1:49 ` [LTP] [PATCH v3 2/4] lib: Introduce KCONFIG_SKIP_CHECK environment variable Yang Xu
2022-01-10 8:14 ` Li Wang
2022-01-10 12:20 ` Cyril Hrubis
2022-01-11 1:38 ` xuyang2018.jy
2022-01-10 1:49 ` [LTP] [PATCH v3 3/4] shell: add kconfig parse api Yang Xu
2022-01-10 8:26 ` Li Wang
2022-01-10 8:46 ` xuyang2018.jy
2022-01-10 9:13 ` Li Wang
2022-01-10 13:43 ` Cyril Hrubis
2022-01-11 5:29 ` xuyang2018.jy
2022-01-11 6:10 ` [LTP] [PATCH v4 1/5] lib/tst_kconfig: Modify the return type of tst_kconfig_check function Yang Xu
2022-01-11 6:10 ` [LTP] [PATCH v4 2/5] lib: Introduce KCONFIG_SKIP_CHECK environment variable Yang Xu
2022-01-13 11:09 ` Petr Vorel
2022-01-14 5:36 ` xuyang2018.jy
2022-01-11 6:10 ` [LTP] [PATCH v4 3/5] shell: add kconfig parse api Yang Xu
2022-01-11 7:52 ` Li Wang
2022-01-11 8:37 ` xuyang2018.jy
2022-01-13 9:15 ` xuyang2018.jy
2022-01-13 9:42 ` Li Wang
2022-01-13 15:51 ` Cyril Hrubis
2022-01-14 6:26 ` xuyang2018.jy
2022-01-14 9:19 ` xuyang2018.jy
2022-01-14 9:49 ` Petr Vorel
2022-01-11 6:10 ` [LTP] [PATCH v4 4/5] sysctl/sysctl02.sh: Use kconfig shell api Yang Xu
2022-01-13 10:53 ` Petr Vorel
2022-01-13 16:06 ` Petr Vorel
2022-01-13 15:54 ` Cyril Hrubis
2022-01-11 6:10 ` [LTP] [PATCH v4 5/5] runtest.sh: add test_kconfig.sh into ltp c test target Yang Xu
2022-01-13 11:25 ` Petr Vorel
2022-01-13 15:54 ` Cyril Hrubis
2022-01-10 1:49 ` [LTP] [PATCH v3 4/4] sysctl/sysctl02.sh: Use kconfig shell api Yang Xu
2022-01-10 8:30 ` Li Wang
2022-01-10 14:15 ` Cyril Hrubis
2022-01-11 5:34 ` xuyang2018.jy
2022-01-10 8:10 ` [LTP] [PATCH v3 1/4] lib/tst_kconfig: Modify the return type of tst_kconfig_check function Li Wang
2022-01-10 12:18 ` Cyril Hrubis
2022-01-10 5:45 ` [LTP] [PATCH v2 4/4] sysctl/sysctl02.sh: Use kconfig shell api xuyang2018.jy
2022-01-06 9:54 ` [LTP] [PATCH v2 1/4] lib/tst_kconfig: Modify the return type of tst_kconfig_check function Petr Vorel
2022-01-06 10:57 ` Cyril Hrubis
2022-01-07 1:25 ` xuyang2018.jy
2022-01-04 6:57 ` [LTP] [PATCH v1 3/3] sysctl/sysctl02.sh: Use kconfig shell api Yang Xu
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=61D79EEE.5030904@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--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