From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/3 v2] tst_supported_fs: Unify messaging
Date: Fri, 23 Sep 2022 08:05:10 +0200 [thread overview]
Message-ID: <Yy1MloHWZ7rSxd+v@pevik> (raw)
In-Reply-To: <CAEemH2enjnO-=VLb8Lq3Gz3MT4_PoOTZBU76S3Z7ojBUdywaew@mail.gmail.com>
Hi Li, all,
> > I'm not sure about this myself. Shouldn't we rather use tst_brk() and
> > tst_res() instead? It's show tst_supported_fs as command.
> Not exactly, looking at testcase/lib/* tools, most of them are not written
> by LTP standard API, some even do not include tst_test.h.
FYI I meant tst_{brk,res} message starts with filename and line, which is kind of handy.
> I personally think if we want more flexibility for those small programs
> as auxiliary tool, we should not apply API as dogmatism for everything.
Sure
> Btw, there is patch confliction when performing git-am, if you can
> rebase accordingly for solving that, the whole patchset will be
> great for me.
I'm sorry, indeed git-am does not work. I remember rebasing it (and my remote
branch is rebased), I obviously must have run git format-patch before rebasing.
In case of anybody want to actually run it, it's in my fork:
https://github.com/pevik/ltp/commits/fix/TST_ALL_FILESYSTEMS.v2
> Reviewed-by: Li Wang <liwang@redhat.com>
Thanks!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-09-23 6:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 21:09 [LTP] [PATCH 0/3 v2] tst_test.sh: Fix filesystem support detection Petr Vorel
2022-09-22 21:09 ` [LTP] [PATCH 1/3 v2] tst_supported_fs: Unify messaging Petr Vorel
2022-09-23 2:43 ` Li Wang
2022-09-23 6:05 ` Petr Vorel [this message]
2022-09-23 15:23 ` Cyril Hrubis
2022-09-23 16:31 ` Petr Vorel
2022-09-22 21:09 ` [LTP] [PATCH 2/3 v2] tst_supported_fs: Fix return codes Petr Vorel
2022-09-22 21:09 ` [LTP] [PATCH 3/3 v2] tst_test.sh: Fix filesystem support detection Petr Vorel
2022-09-23 15:29 ` Cyril Hrubis
2022-09-23 16:36 ` Petr Vorel
2022-09-26 9:13 ` Cyril Hrubis
2022-09-26 9:34 ` Petr Vorel
2022-09-26 9:45 ` 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=Yy1MloHWZ7rSxd+v@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--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.