From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <wangli.ahau@gmail.com>
Cc: lufei <lufei@uniontech.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5] Rewrite ftrace_regression tests with new C API
Date: Tue, 28 Apr 2026 09:33:36 +0200 [thread overview]
Message-ID: <afBi0ESzhNDhWdiP@yuki.lan> (raw)
In-Reply-To: <CANgNiRyqbihyqbf9UVoPDq_Gi9uEzJ_KXJ96SoGQHE+vp=ag=Q@mail.gmail.com>
Hi!
> > + SAFE_FILE_PRINTF(page_fault_path, "%d", page_fault_origin);
> > +
> > + tst_res(TPASS, "Test passed for setting userstacktrace "
> > + "bug(preempt count leak) not reproduced"
> > + );
>
> No need put the ")" in a new line.
>
> tst_res(TPASS, "Test passed for setting userstacktrace "
> - "bug(preempt count leak) not reproduced"
> - );
> + "bug(preempt count leak) not reproduced");
Or even better, keep the message short and to the point with just:
tst_res(TPASS, "Preempt count leak bug not reproduced");
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-28 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 8:05 [LTP] [PATCH 1/2] Rewrite ftrace_regression01.sh with new C API lufei
2026-03-04 8:05 ` [LTP] [PATCH 2/2] Rewrite ftrace_regression02.sh " lufei
2026-03-27 10:34 ` [LTP] [PATCH 1/2] Rewrite ftrace_regression01.sh " Andrea Cervesato via ltp
2026-03-30 7:15 ` [LTP] [PATCH v2] Rewrite ftrace_regression tests " lufei
2026-03-30 8:39 ` Andrea Cervesato via ltp
2026-03-31 1:55 ` [LTP] [PATCH v3] " lufei
2026-03-31 7:53 ` Petr Vorel
2026-03-31 7:56 ` Petr Vorel
2026-03-31 18:28 ` Cyril Hrubis
2026-03-31 10:01 ` [LTP] [PATCH v4] " lufei
2026-04-24 2:08 ` [LTP] [PATCH v5] " lufei
2026-04-24 2:42 ` [LTP] " linuxtestproject.agent
2026-04-27 8:40 ` [LTP] [PATCH v5] " Li Wang
2026-04-28 7:33 ` Cyril Hrubis [this message]
2026-04-28 7:50 ` [LTP] [PATCH v6] " lufei
2026-04-28 9:30 ` [LTP] " linuxtestproject.agent
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=afBi0ESzhNDhWdiP@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=lufei@uniontech.com \
--cc=wangli.ahau@gmail.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