From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v1 2/3] shell: add kconfig parse api
Date: Thu, 6 Jan 2022 08:16:32 +0000 [thread overview]
Message-ID: <61D6A588.8060609@fujitsu.com> (raw)
In-Reply-To: <61D6857F.9060802@fujitsu.com>
Hi Petr
>>>>> +
>>>>> +Now, we support the length of kconfig list is 10.
>>>> Why 10? Cyril suggested that in PR, where he suggested to use separated
>>>> variables:
>>>> https://github.com/linux-test-project/ltp/issues/891#issuecomment-989712350
>>
>>>> But for string used like array there is no performance limitation, thus I'd use
>>>> something like 50 or 100. Because for certain IMA tests there are at least 6
>>>> kconfig requirements, thus> 10 could be hit.
>>> If case needs more than 10 kconfigs, we can use& ie
>>> "CONFIG_EX4_FS& CONFIG_XFS_FS& CONFIG_QUOTAL_FS, CONFIG_PROC_FS..."
>> Sure. I just meant there is no reason to put low number and then workaround it.
From my understanding, we split kconfig list for kconfig1,2... variables.
Then I need to call tst_check_kconfigs with pass fixed number paremeters
one ie 10). code ie
tst_check_kconfigs $kconfig1 $kconfig2 $kconfig3 $kconfig4 $kconfig5
$kconfig6\
$kconfig7 $kconfig8 $kconfig9 $kconfig10
So do you have simple code to replace them or you just want to increase
the number to 20?
ps: In fact, I am not good at writting shell script. So if wrong or have
better way, please tell me.
Best Regards
Yang Xu
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-06 8:16 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 [this message]
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
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=61D6A588.8060609@fujitsu.com \
--to=xuyang2018.jy@fujitsu.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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