All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] doc: Add missing API references to api_c_tests.rst
Date: Thu,  4 Jun 2026 09:34:51 +0000	[thread overview]
Message-ID: <20260604093451.4058-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260604-doc_add_missing_headers-v5-1-2e0adc082d5a@suse.com>

Hi Andrea,

On Thu, 04 Jun 2026 10:45:08 +0200, Andrea Cervesato wrote:
> doc: Add missing API references to api_c_tests.rst

--- [PATCH 1/3] ---

> +/**
> + * struct tst_device - Block device used by a test.
>   ...
>  */
>  struct tst_device {
>  ...
>  /*
> - * Automatically initialized if test.needs_device is set.
> + * tst_device - Pointer to the test block device.
> + *
> + * Automatically initialized if tst_test.needs_device is set.
>   */
>  extern struct tst_device *tst_device;

The tst_device variable comment body was updated to kernel-doc format
(starting with "tst_device - ..."), but the opening delimiter was left
as "/*" instead of "/**". kernel-doc ignores "/*" blocks, so this
variable will not appear in the generated documentation. Every other
function in this file was converted with "/**" in the same commit.

> +Filesystems
> +-----------
> +.. kernel-doc:: ../../include/tst_fs.h
>
> ...
>
> +Memory
> +------
> +.. kernel-doc:: ../../include/tst_memutils.h

tst_fs.h and tst_memutils.h were not converted to kernel-doc format in
this commit. tst_fs.h has a single "/**" comment for tst_path_exists(),
and tst_memutils.h has one for tst_mapping_in_range(). The primary APIs
in each header -- tst_fs_type(), tst_fs_has_free(), tst_pollute_memory(),
tst_available_mem(), tst_available_swap() -- all use plain "/*" comments
and will not be extracted.

The resulting "Filesystems" and "Memory" sections under LTP C API will
each document only one function, neither of which is the main API the
section title implies.

Was the intent to convert these headers in a follow-up, or should they
be converted here to avoid publishing sparse documentation sections?

Verdict: Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-06-04  9:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04  8:45 [LTP] [PATCH v5 0/3] Complete the documentation adding missing headers Andrea Cervesato
2026-06-04  8:45 ` [LTP] [PATCH v5 1/3] doc: Add missing API references to api_c_tests.rst Andrea Cervesato
2026-06-04  9:34   ` linuxtestproject.agent [this message]
2026-06-04 10:17   ` [LTP] " linuxtestproject.agent
2026-06-04  8:45 ` [LTP] [PATCH v5 2/3] doc: Complete struct tst_test table and shell API docs Andrea Cervesato
2026-06-04  8:45 ` [LTP] [PATCH v5 3/3] doc: Add SAFE_* macros reference page Andrea Cervesato
  -- strict thread matches above, loose matches on Subject: below --
2026-06-05  9:17 [LTP] [PATCH v6 1/3] doc: Add missing API references to api_c_tests.rst Andrea Cervesato
2026-06-05  9:30 ` [LTP] " linuxtestproject.agent
2026-06-05  9:39   ` Andrea Cervesato via ltp
2026-06-03  9:56 [LTP] [PATCH v4 1/3] " Andrea Cervesato
2026-06-03 14:40 ` [LTP] " linuxtestproject.agent
2026-06-02 15:49 [LTP] [PATCH v3 1/3] " Andrea Cervesato
2026-06-02 17:34 ` [LTP] " linuxtestproject.agent
2026-06-02 10:09 [LTP] [PATCH v2 1/3] " Andrea Cervesato
2026-06-02 11:40 ` [LTP] " linuxtestproject.agent
2026-06-01 10:36 [LTP] [PATCH 1/3] " Andrea Cervesato
2026-06-01 13:41 ` [LTP] " linuxtestproject.agent
2026-06-01 13:56   ` Andrea Cervesato 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=20260604093451.4058-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.