From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] inode: convert to new API and merge into a single test
Date: Fri, 17 Jul 2026 11:14:13 +0200 [thread overview]
Message-ID: <alnyZYfYiEhNBJ5i@yuki.lan> (raw)
In-Reply-To: <20260716-rewrite_inode_testing_suite-v1-1-b6fee6f0d0ba@suse.com>
Hi!
> The inode01 and inode02 tests shared the same directory/file tree engine
> and differed only in tree dimensions and in whether the workload ran in
> a single process or across several parallel workers.
>
> inode01 now covers both scenarios, so inode02 is removed together with
> its entries in runtest/fs, runtest/fs_readonly and the .gitignore. Note
> this drops inode02 as a test id; its runtest/fs_readonly slot is left as
> a gap so unrelated test_robind entries keep their numbers.
>
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> runtest/fs | 1 -
> runtest/fs_readonly | 1 -
> testcases/kernel/fs/inode/.gitignore | 1 -
> testcases/kernel/fs/inode/inode01.c | 864 +++++----------------------------
> testcases/kernel/fs/inode/inode02.c | 902 -----------------------------------
Just FYI diffs for big rewrites like this are much more readable if
generated with the git -B switch.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-07-17 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 9:43 [LTP] [PATCH] inode: convert to new API and merge into a single test Andrea Cervesato
2026-07-16 13:15 ` [LTP] " linuxtestproject.agent
2026-07-17 9:14 ` Cyril Hrubis [this message]
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=alnyZYfYiEhNBJ5i@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.