From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Andrea Cervesato" <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP old API conversion
Date: Wed, 18 Mar 2026 13:04:07 +0000 [thread overview]
Message-ID: <69baa2c8.050a0220.3719be.4e9a@mx.google.com> (raw)
In-Reply-To: <69b97807.050a0220.26befa.70b8@mx.google.com>
> An another thing is how we want to push these patches in the repository. At the
> moment kernel is using some special tags to identify if patches have been
> generated by LLMs or by humans. This is something we should think about,
> because we already have a few examples recently (i.e. your ulimit01, newuname01
> tests and my listns() testing suite) where LLMs where doing most of the job.
> Also, we are receiving more and more patches which seem to be written by AI.
What about this ?
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-18 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 10:42 [LTP] LTP old API conversion Andrea Cervesato via ltp
2026-03-17 11:58 ` Petr Vorel
2026-03-17 12:14 ` Andrea Cervesato via ltp
2026-03-17 22:39 ` Petr Vorel
2026-03-18 5:36 ` Li Wang via ltp
2026-03-17 15:32 ` Cyril Hrubis
2026-03-17 15:49 ` Andrea Cervesato via ltp
2026-03-18 13:04 ` Andrea Cervesato via ltp [this message]
2026-03-18 5:18 ` Li Wang via ltp
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=69baa2c8.050a0220.3719be.4e9a@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.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