From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 2/4] lib: Add support for TDBUG tst_res() flag
Date: Fri, 8 Dec 2023 08:43:06 +0100 [thread overview]
Message-ID: <20231208074306.GA314880@pevik> (raw)
In-Reply-To: <CAASaF6yheXD4w07K1xUVXrqoS6jdX6PUjG64UXQbE_hQR9cW7w@mail.gmail.com>
Hi Jan, all,
> > diff --git a/doc/C-Test-API.asciidoc b/doc/C-Test-API.asciidoc
> > index dab811564..479179263 100644
> > --- a/doc/C-Test-API.asciidoc
> > +++ b/doc/C-Test-API.asciidoc
> > @@ -227,6 +227,7 @@ Printf-like function to report test result, it's mostly used with ttype:
> > | 'TPASS' | Test has passed.
> > | 'TFAIL' | Test has failed.
> > | 'TINFO' | General message.
> > +| 'TDBUG' | Debug message (C API only, printed with '-v').
> My first impression was it's some kind of new BUG type :-)
> I'd suggest making it TDEBUG or TDBG.
Agree it looks strange. We wanted to keep 5 letters.
Therefore maybe TVERB (in discussion from v1).
If we agree to use more, TDEBUG or TVERBOSE would be better.
Kind regards,
Petr
> > | 'TWARN' | Something went wrong but we decided to continue. Mostly used in cleanup functions.
> > |==============================
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-12-08 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 21:27 [LTP] [PATCH v2 0/4] Add TDBUG tst_res() flag Petr Vorel
2023-12-07 21:27 ` [LTP] [PATCH v2 1/4] lib/tests: Add test for testing tst_res() flags Petr Vorel
2023-12-07 21:27 ` [LTP] [PATCH v2 2/4] lib: Add support for TDBUG tst_res() flag Petr Vorel
2023-12-08 6:50 ` Jan Stancek
2023-12-08 7:43 ` Petr Vorel [this message]
2023-12-08 8:17 ` Cyril Hrubis
2023-12-08 13:53 ` Petr Vorel
2023-12-08 13:54 ` Andrea Cervesato via ltp
2023-12-07 21:27 ` [LTP] [PATCH v2 3/4] fsx-linux: Reduce log output with TDBUG Petr Vorel
2023-12-07 21:27 ` [LTP] [PATCH v2 4/4] fsx-linux: Use SAFE_MSYNC() 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=20231208074306.GA314880@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox