From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Petr Vorel" <pvorel@suse.cz>,
"Andrea Cervesato" <andrea.cervesato@suse.de>,
"Linux Test Project" <ltp@lists.linux.it>,
"Cyril Hrubis" <chrubis@suse.cz>
Subject: Re: [LTP] [PATCH v2] Remove runltp `scenario_groups` leftovers
Date: Tue, 24 Feb 2026 09:55:57 +0100 [thread overview]
Message-ID: <DGN2EOO6ZQXW.2593AWA6WTL4T@suse.com> (raw)
In-Reply-To: <20260224083107.GC28159@pevik>
On Tue Feb 24, 2026 at 9:31 AM CET, Petr Vorel wrote:
> > Hi Andrea,
>
> > > Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> > > ---
> > > Changes in v2:
> > > - forgot to keep runltp script
> > > - Link to v1: https://lore.kernel.org/r/20260224-remove_runltp-v1-1-7baa79b65acd@suse.com
> > > ---
> > > scenario_groups/Makefile | 38 --------------------------------------
> > > scenario_groups/default | 28 ----------------------------
> > > scenario_groups/network | 20 --------------------
>
> > I thought people are using scenario_groups as kind of list of runtest files.
> > But maybe I'm wrong.
>
> > Also, you need to modify top level Makefile, otherwise make install/clean fails.
> > => v3 or don't forget to fix before merge.
>
> Actually also doc/developers/writing_tests.rst mentions scenario_groups.
>
> Kind regards,
> Petr
>
> > Kind regards,
> > Petr
>
> > > 3 files changed, 86 deletions(-)
I'm having some bugs in the grep utility at the moment. I guess it's not
in-sync with neovim and having issues to spot all strings inside files.
Sorry for missing this doc thingy. I will fix it on v4...
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-02-24 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 8:19 [LTP] [PATCH v2] Remove runltp `scenario_groups` leftovers Andrea Cervesato
2026-02-24 8:30 ` Petr Vorel
2026-02-24 8:31 ` Petr Vorel
2026-02-24 8:55 ` Andrea Cervesato via ltp [this message]
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=DGN2EOO6ZQXW.2593AWA6WTL4T@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=andrea.cervesato@suse.de \
--cc=chrubis@suse.cz \
--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