All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Jan Kara <jack@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] ioctl_loop01.c: Use proper device for partitioning
Date: Wed, 24 Sep 2025 14:55:01 +0200	[thread overview]
Message-ID: <20250924125501.GA70531@pevik> (raw)
In-Reply-To: <aNPN9N-Zadq0h7Vs@yuki.lan>

> Hi!
> > If we select option 2 then we have following setting for all related
> > test cases.
> > +       .needs_cmds = (const struct tst_cmd[]) {
> > +               {"parted", "0"},
> > +               {}
> > +       },

> > But how to get "parted" command support status? In ioctl_loop01.c there
> > is a local var "parted_sup" which flag parted command support or not, and
> > use this flag to decide which sub test needed. 
> > If we do this logic in test lib then we need create another
> > flag in tst_cmd used for give status of command support or not.
> > During test lib logic will set tst_cmd.support flag.

> >  struct tst_cmd {
> >  	const char *cmd;
> >  	unsigned int required:1;
> >  	unsigned int support:1;
> >  };

> > Correct me if any misunderstanding, many thanks.

> Sounds reasonable and we could also add a nice function to the test
> library:

> bool tst_cmd_present(const char *cmd);

> that would loop over the tst_cmd array and return the supported flag
> value.

+1, although not sure if we want to finish this before the release.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-09-24 12:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01  7:47 [LTP] [PATCH v1] ioctl_loop01.c: Use proper device for partitioning Wei Gao via ltp
2025-09-01 10:38 ` Petr Vorel
2025-09-02  2:16   ` Wei Gao via ltp
2025-09-02  3:12 ` [LTP] [PATCH v2] " Wei Gao via ltp
2025-09-02 10:44   ` Petr Vorel
2025-09-02 11:18   ` [LTP] [PATCH v3] " Wei Gao via ltp
2025-09-03 12:48     ` Petr Vorel
2025-09-09 11:50     ` Cyril Hrubis
2025-09-10  1:35       ` Wei Gao via ltp
2025-09-18 14:53         ` Petr Vorel
2025-09-18 15:35           ` Cyril Hrubis
2025-09-19 13:22             ` Petr Vorel
2025-09-22  7:28               ` Cyril Hrubis
2025-09-22  7:32                 ` Petr Vorel
2025-09-24  2:26             ` Wei Gao via ltp
2025-09-24  7:03               ` Petr Vorel
2025-09-24  9:54               ` Cyril Hrubis
2025-09-24 10:40                 ` Wei Gao via ltp
2025-09-24 10:54                   ` Cyril Hrubis
2025-09-24 12:55                     ` Petr Vorel [this message]
2025-09-24 13:17                       ` Cyril Hrubis

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=20250924125501.GA70531@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=jack@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 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.