From: Avinesh Kumar <akumar@suse.de>
To: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] doc: Improve .skip_filesystems documentation
Date: Fri, 07 Oct 2022 19:34:36 +0530 [thread overview]
Message-ID: <4450243.LvFx2qVVIh@localhost> (raw)
In-Reply-To: <20221006102900.3246-1-pvorel@suse.cz>
Hi Petr,
On Thursday, October 6, 2022 3:59:00 PM IST Petr Vorel wrote:
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> doc/c-test-api.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/doc/c-test-api.txt b/doc/c-test-api.txt
> index 64ee3397f..2865160cc 100644
> --- a/doc/c-test-api.txt
> +++ b/doc/c-test-api.txt
> @@ -894,6 +894,15 @@ If test needs to adjust expectations based on filesystem type it's also
> possible to detect filesystem type at the runtime. This is preferably used
> when only subset of the test is not applicable for a given filesystem.
>
> +NOTE: ext2, ext3 or ext4 in '.skip_filesystems' on tests which does *not* use
> + '.all_filesystems' needs to be defined as 'ext2/ext3/ext4'. The reason
> + is that is hard to detect used filesystem due overlapping the functionality.
nit:
s/that is/that it is
s/due/due to
> + OTOH tests which use '.skip_filesystems' *with* '.all_filesystems' can skip
> + only filesystems which are actually used in '.all_filesystems': ext2, ext3,
> + ext4, xfs, btrfs, vfat, exfat, ntfs, tmpfs (defined in 'fs_type_whitelist[]').
> + It does not make sense to list other filesystems.
> +
> +
> [source,c]
> -------------------------------------------------------------------------------
> #include "tst_test.h"
>
Reviewed-by: Avinesh Kumar <akumar@suse.de>
Regards,
Avinesh
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-10-07 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 10:29 [LTP] [PATCH 1/1] doc: Improve .skip_filesystems documentation Petr Vorel
2022-10-07 14:04 ` Avinesh Kumar [this message]
2022-10-07 21:11 ` Petr Vorel
2022-11-01 13:17 ` Richard Palethorpe
2022-11-01 13:25 ` 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=4450243.LvFx2qVVIh@localhost \
--to=akumar@suse.de \
--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