public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] lib: tst_kconfig: Add runtime checks
Date: Thu, 26 Mar 2026 15:09:49 +0100	[thread overview]
Message-ID: <acU-LbVnVWoNwvwm@yuki.lan> (raw)
In-Reply-To: <CAEemH2fDFBzoMvkZ_ZDPFCZVyMn2Dq0Ro6xBLTELRTK24Ey6eg@mail.gmail.com>

Hi!
> > IMHO that's why ssh supports multiple '-v', e.g. '-v -v -v' or '-vvv'
> > instead of
> > -v2 or -v3).
> >
> > Anyway I'd prefer solving this somehow in the code so that users don't
> > have to
> > bother about log levels, but I have no idea how. Maybe yet another enum
> > tst_res_flags member? Because aa5a6fcdcd skipped messages, which are likely
> > useful when run by child process (the test), but not by library process.
> > And I
> > want to print message which is always run by library process. Maybe to
> > have some
> > #define in source code, which would force logging even for library
> > process? (not
> > sure what will be needed more often).
> >
> 
> This is something worth thinking about carefully, btw, next week is
> our spring festival hoday. I maybe reply you a bit later :).

Did we reach any conclusion here?

I think that we should implement different debug levels in LTP and drop
LTP_QUIET in the process. Does that sounds reasonable?

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2026-03-26 14:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 13:57 [LTP] [PATCH] lib: tst_kconfig: Add runtime checks Cyril Hrubis
2026-02-05 17:47 ` Petr Vorel
2026-02-06  7:58   ` Li Wang via ltp
2026-02-06  8:23     ` Petr Vorel
2026-02-06 12:23       ` Li Wang via ltp
2026-03-26 14:09         ` Cyril Hrubis [this message]
2026-03-26 14:16           ` Cyril Hrubis
2026-03-26 16:39           ` Petr Vorel
2026-02-06  8:23     ` Petr Vorel
2026-02-06  8:33     ` Cyril Hrubis
2026-02-06  9:31       ` Petr Vorel
2026-02-06  9:37       ` Petr Vorel
2026-02-06  9:45         ` Cyril Hrubis
2026-02-06 10:31           ` Petr Vorel
2026-03-26 14:38   ` Cyril Hrubis
2026-03-26 15:44     ` Petr Vorel
2026-03-11  8:59 ` Petr Vorel
2026-03-24  8:33 ` Andrea Cervesato via ltp
2026-03-26 14:17   ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2026-03-26 14:40 Cyril Hrubis
2026-03-26 15:15 ` Petr Vorel
2026-03-27  7:02 ` Li Wang via ltp
2026-03-27 11:06   ` 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=acU-LbVnVWoNwvwm@yuki.lan \
    --to=chrubis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox