From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Cyril Hrubis <chrubis@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] Formal kernel API specification
Date: Thu, 19 Jun 2025 11:39:12 +0200 [thread overview]
Message-ID: <f1965005-0f90-4404-afe2-e22a0d2b66c2@suse.com> (raw)
In-Reply-To: <aFPRA7FkfMgeb-FA@yuki.lan>
Hi!
On 6/19/25 10:57, Cyril Hrubis wrote:
> Hi!
> I just stumbled upon:
>
> https://www.phoronix.com/news/Linux-API-Spec-Framework
>
> I will have a closer look at the patchset but it looks like it may be
> able to generate LTP tests based on the specification, which would be
> awesome.
>
Really good news. I hope it will be merged soon since it would be
beneficial for arguments validation tests for sure.
The generation of these specific tests shouldn't be a big challenge
then, just before compiling all the binaries.
- Andrea
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-06-19 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 8:57 [LTP] Formal kernel API specification Cyril Hrubis
2025-06-19 9:39 ` 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=f1965005-0f90-4404-afe2-e22a0d2b66c2@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=chrubis@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