From: linuxtestproject.agent@gmail.com
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lib: Ignore empty LTP_ENABLE_DEBUG
Date: Thu, 23 Apr 2026 09:36:50 +0000 [thread overview]
Message-ID: <20260423093650.4027-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260423084123.657690-2-pvorel@suse.cz>
Hi Petr,
--- [PATCH 5/6] ---
On 2026-04-23, Petr Vorel wrote:
> lib: Merge functionality of LTP_QUIET into LTP_REPRODUCIBLE_OUTPUT
> + - When set to ``1`` or ``y`` uppress printing TCONF, TINFO and TDEBUG
s/uppress/suppress/
(The typo is carried into patch 6/6 as well.)
---
Note:
Our agent completed the review of the patch. The agent can sometimes
produce false positives although often its findings are genuine. If you
find issues with the review, please comment this email or ignore the
suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-23 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 8:41 [LTP] [PATCH v5 0/6] lib: LTP_DEBUG cleanup Petr Vorel
2026-04-23 8:41 ` [LTP] [PATCH v5 1/6] lib: Ignore empty LTP_ENABLE_DEBUG Petr Vorel
2026-04-23 9:36 ` linuxtestproject.agent [this message]
2026-04-23 8:41 ` [LTP] [PATCH v5 2/6] lib: Rename variable LTP_ENABLE_DEBUG => LTP_DEBUG Petr Vorel
2026-04-23 8:41 ` [LTP] [PATCH v5 3/6] lib: Prefer LTP_DEBUG over -D Petr Vorel
2026-04-23 8:41 ` [LTP] [PATCH v5 4/6] doc: newlib_tests: Update debugging parameters Petr Vorel
2026-04-23 8:41 ` [LTP] [PATCH v5 5/6] lib: Merge functionality of LTP_QUIET into LTP_REPRODUCIBLE_OUTPUT Petr Vorel
2026-04-23 9:38 ` Petr Vorel
2026-04-23 8:41 ` [LTP] [PATCH v5 6/6] lib: Print TCONF on LTP_REPRODUCIBLE_OUTPUT=1 Petr Vorel
2026-04-23 9:39 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2026-04-22 14:12 [LTP] [PATCH v4 1/5] lib: Ignore empty LTP_ENABLE_DEBUG Petr Vorel
2026-04-22 15:18 ` [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=20260423093650.4027-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@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