From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] fsconfig04.c: Check FSCONFIG_SET_PATH
Date: Mon, 16 Mar 2026 09:49:20 +0100 [thread overview]
Message-ID: <20260316084920.GA291437@pevik> (raw)
In-Reply-To: <aZ7Am0YgYLK33spn@autotest-wegao.qe.prg2.suse.org>
Hi Andrea, Wei,
> On Fri, Dec 12, 2025 at 10:29:35AM +0100, Andrea Cervesato wrote:
> > Hi!
> > please, re-read the previous reviews before submitting a new version,
> > because there are still some issues not achieved.
If you *were* a concrete what is wrong, you'd have saved Wei's and my time :).
> Thanks for take a look.
> I think Cyril comments should be fixed in current version after recheck, so i move patch into
> Needs Review in patchwork again.
I'd also say all issues has been fixed. What exactly do you mean?
Also, test needs rebase after Wei's and Li's changes to fix compilation.
Kind regards,
Petr
+++ testcases/kernel/syscalls/fsconfig/fsconfig04.c
@@ -24,7 +24,7 @@
#include "tst_test.h"
#include "lapi/fsmount.h"
-#include "old/old_device.h"
+#include "old/tso_device.h"
#define MNTPOINT "mntpoint"
#define LOOP_DEV_SIZE 10
@@ -150,9 +150,9 @@ static struct tst_test test = {
.needs_root = 1,
.format_device = 1,
.mntpoint = MNTPOINT,
- .needs_cmds = (const char *[]) {
- "tune2fs",
- NULL
+ .needs_cmds = (struct tst_cmd[]) {
+ {.cmd = "tune2fs"},
+ {}
},
.filesystems = (struct tst_fs []) {
{.type = "ext3"},
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-16 8:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 15:10 [LTP] [PATCH v1] fsconfig04.c: Check FSCONFIG_SET_PATH Wei Gao via ltp
2025-05-22 20:56 ` Petr Vorel
2025-05-26 14:29 ` Wei Gao via ltp
2025-05-26 6:40 ` Petr Vorel
2025-05-26 14:35 ` [LTP] [PATCH v2] " Wei Gao via ltp
2025-05-26 9:54 ` Petr Vorel
2025-05-26 12:54 ` Cyril Hrubis
2025-05-26 16:13 ` Petr Vorel
2025-05-27 8:24 ` Cyril Hrubis
2025-05-27 8:58 ` [LTP] LTP doc: test examples [was: Re: [PATCH v2] fsconfig04.c: Check FSCONFIG_SET_PATH] Petr Vorel
2025-05-26 14:38 ` [LTP] [PATCH v2] fsconfig04.c: Check FSCONFIG_SET_PATH Cyril Hrubis
2025-06-03 21:45 ` [LTP] [PATCH v3] " Wei Gao via ltp
2025-10-17 4:39 ` Wei Gao via ltp
2025-12-12 9:29 ` Andrea Cervesato via ltp
2026-02-25 9:27 ` Wei Gao via ltp
2026-03-16 8:49 ` Petr Vorel [this message]
2026-03-17 0:59 ` Wei Gao via ltp
2026-03-24 12:50 ` 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=20260316084920.GA291437@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=wegao@suse.com \
/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