+------------
+The Documentation/doc-guide/kernel-doc.rst chapter describes how to document
the code using the kernel-doc format, however it does not specify the criteria
to be followed for writing testable specifications; i.e. specifications that
can be used to for the semantic description of low level requirements.
Please, for any future versions, stick to the 80-column limit; this is
especially important for text files that you want humans to read.
As a nit, you don't need to start by saying what other documents don't
do, just describe the purpose of *this* document.
More substantially ... I got a way into this document before realizing
that you were describing an addition to the format of kerneldoc
comments. That would be good to make clear from the outset.
What I still don't really understand is what is the *purpose* of this
formalized text? What will be consuming it? You're asking for a fair
amount of effort to write and maintain these descriptions; what's in it
for the people who do that work?
I might be wrong, but sounds to me like someone intends to feed this to
AI to generate tests or code.
In that case, no thanks.
I'm pretty sure we don't want this.
--
Cheers
David / dhildenb
