From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Martin Doucha <martin.doucha@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/2] mkswap01: wait for the triggered events to complete
Date: Wed, 20 Apr 2022 22:56:20 +0200 [thread overview]
Message-ID: <YmBzdLLeX3kNfbvu@pevik> (raw)
In-Reply-To: <20220420114720.1463473-2-liwang@redhat.com>
Hi all,
> Signed-off-by: Li Wang <liwang@redhat.com>
> ---
> testcases/commands/mkswap/mkswap01.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/testcases/commands/mkswap/mkswap01.sh b/testcases/commands/mkswap/mkswap01.sh
> index f6494f6e3..cb3563b49 100755
> --- a/testcases/commands/mkswap/mkswap01.sh
> +++ b/testcases/commands/mkswap/mkswap01.sh
> @@ -128,7 +128,7 @@ mkswap_test()
> return
> fi
> - udevadm trigger --name-match=$TST_DEVICE
> + udevadm trigger --name-match=$TST_DEVICE --settle
> if [ -n "$device" ]; then
> mkswap_verify "$mkswap_op" "$op_arg" "$device" "$size" "$dev_file"
--settle option for udevadm trigger has been added in v238 (in 2018) [1].
This mean on SLES 12-SP5, RHEL-7.9, 18.04 LTS bionic, ... we get:
trigger: unrecognized option '--settle'
Do we ignore backward compatibility hoping that all distros aren't tested with
newer LTP?
Kind regards,
Petr
[1] https://github.com/systemd/systemd/commit/792cc203a67edb201073351f5c766fce3d5eab45
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-04-20 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 11:47 [LTP] [PATCH 1/2] ioctl09: wait for udevd complete the uevent handling Li Wang
2022-04-20 11:47 ` [LTP] [PATCH 2/2] mkswap01: wait for the triggered events to complete Li Wang
2022-04-20 12:07 ` Cyril Hrubis
2022-04-20 20:56 ` Petr Vorel [this message]
2022-04-21 2:18 ` Li Wang
2022-04-21 6:44 ` Li Wang
2022-04-21 7:47 ` Petr Vorel
2022-04-20 12:05 ` [LTP] [PATCH 1/2] ioctl09: wait for udevd complete the uevent handling Cyril Hrubis
2022-04-20 12:31 ` Li Wang
2022-04-20 12:52 ` Cyril Hrubis
2022-04-21 6:36 ` Li Wang
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=YmBzdLLeX3kNfbvu@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@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