From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v6] agents: Add AI agent configuration for code reviews
Date: Mon, 9 Mar 2026 15:42:36 +0100 [thread overview]
Message-ID: <20260309144236.GA28075@pevik> (raw)
In-Reply-To: <20260224-agents_file-v6-1-db15c490d048@suse.com>
Hi Andrea,
thanks for your work. On a first look LGTM.
Acked-by: Petr Vorel <pvorel@suse.cz>
I wonder if we can somehow avoid duplicity with our Ground Rules
https://linux-test-project.readthedocs.io/en/latest/developers/ground_rules.html
Ideally text would be just in a single document.
...
> +### 6. Safe Macros
> +
> +- MUST use `SAFE_*` macros for system calls that must not fail
> +- Safe macros are defined in `include/` directory
Actually the signatures are defined there, the code mostly not, but that's minor
detail.
> +
> +### 7. Kernel Version Handling
> +
> +- MUST use `.min_kver` for kernel version gating
> +- MUST prefer runtime checks over compile-time checks
...
I guess I should send v2 for my patch and that could be updated here
https://patchwork.ozlabs.org/project/ltp/patch/20260128080121.18878-1-pvorel@suse.cz/
https://lore.kernel.org/ltp/20260128080121.18878-1-pvorel@suse.cz/
> +
> +### 13. Deprecated Features
> +
> +- MUST NOT define `[Description]` in the test description section
When we handle details like this, we may want to add rule to avoid unnecessary
tags e.g. .mount_device:
metadata/metaparse.c
static struct implies {
const char *flag;
const char **implies;
} implies[] = {
{"mount_device", (const char *[]) {"format_device", "needs_device",
"needs_tmpdir", NULL}},
{"format_device", (const char *[]) {"needs_device", "needs_tmpdir",
NULL}},
{"all_filesystems", (const char *[]) {"needs_device", "needs_tmpdir",
NULL}},
{"needs_device", (const char *[]) {"needs_tmpdir", NULL}},
{"needs_checkpoints", (const char *[]) {"needs_tmpdir", NULL}},
{"resource_files", (const char *[]) {"needs_tmpdir", NULL}},
{NULL, (const char *[]) {NULL}}
};
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-09 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 13:15 [LTP] [PATCH v6] agents: Add AI agent configuration for code reviews Andrea Cervesato
2026-03-09 14:42 ` Petr Vorel [this message]
2026-03-09 14:56 ` Andrea Cervesato via ltp
2026-03-10 11:20 ` 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=20260309144236.GA28075@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--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