public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] tst_supported_fs: Implement checking paths against skiplist
Date: Thu, 22 Sep 2022 10:43:33 +0200	[thread overview]
Message-ID: <YywgNSfv58iIvFbq@pevik> (raw)
In-Reply-To: <b1a19673-de0b-d6e0-0434-3eb457aaf69d@suse.cz>

> On 22. 09. 22 6:16, Li Wang wrote:
> >                      if (skiplist) {
> >     -                       if (tst_fs_in_skiplist(argv[optind], (const char * const*)skiplist))
> >     -                               tst_brk(TCONF, "%s is skipped", argv[optind]);
> >     +                       if (tst_fs_in_skiplist(fsname, (const char * const*)skiplist))
> >     +                               tst_brk(TCONF, "%s is skipped", fsname);


> > TCONF does not means return 1, we might need explicitly 'return 1' here.

> Yes, but that's a problem which already existed before my patch and affects
> the other single-FS checks as well. The fix should go into a separate patch
> after release.

Yes, that's not related. I changed it in eb47b4497 ("tst_supported_fs: Support
skip list when query single fs") as with 32 one can detect it's TCONF.
As long as 0 is success, non-zero for failure.
But I forget to update doc.

Thus I'll wait for feedback from others whether we should get back to 1 as error
(thus use TINFO) or update doc to mention to exit 32 (or more generally non-zero
exit).
very nit: I'd use exit instead of return in docs.

Kind regards,
Petr

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

  reply	other threads:[~2022-09-22  8:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 15:50 [LTP] [PATCH] tst_supported_fs: Implement checking paths against skiplist Martin Doucha
2022-09-22  4:16 ` Li Wang
2022-09-22  8:14   ` Martin Doucha
2022-09-22  8:43     ` Petr Vorel [this message]
2022-09-22  9:08       ` Li Wang
2022-09-22  9:56         ` Petr Vorel
2022-09-22  9:02   ` Petr Vorel
2022-09-22  9:24     ` Li Wang
2022-09-22 10:40       ` Petr Vorel
2022-09-22 10:55         ` Cyril Hrubis
2022-09-22 10:57           ` Martin Doucha
2022-09-22 11:20             ` Petr Vorel
2022-09-22 14:42               ` Cyril Hrubis
2022-09-22 20:22                 ` Petr Vorel
2022-09-22  8:56 ` Petr Vorel
2022-09-22 20:26 ` Petr Vorel
2022-09-23 10:00 ` Petr Vorel
2022-09-26  7:48   ` Petr Vorel
2022-09-23 15: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=YywgNSfv58iIvFbq@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    /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