Linux Test Project
 help / color / mirror / Atom feed
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 3/4] include: Fix kernel-doc warnings in header comments
Date: Mon, 1 Jun 2026 16:09:01 +0200	[thread overview]
Message-ID: <20260601140901.GD3391768@pevik> (raw)
In-Reply-To: <20260601-doc_update-v1-3-b0f59834fbae@suse.com>

Hi Andrea,

> Drop :ref: cross-references to undocumented structs in tst_test.h
> and tst_kvercmp.h kernel-doc comments, replacing them with plain
> text. These produced 'undefined label' Sphinx warnings.

+1, that goes under me I guess. I checked that at the time, but I did not get it
would work without :ref:.

Fixes: b7df4320b0 ("tst_test.h: Link various structs in sphinx doc")
Fixes: 597613727a ("doc: Convert tst_kvercmp.h to RST")
Reviewed-by: Petr Vorel <pvorel@suse.cz>

> Downgrade kernel-doc comments to plain comments for struct tst_cmd
> and TST_CAP() macro to avoid name collisions with the tst_cmd()
> function and struct tst_cap respectively. The kernel-doc parser
> flattens names case-insensitively, causing 'name used several times'
> errors and duplicate target warnings.

Hm ...

...
> +++ b/include/tst_capability.h
> @@ -67,7 +67,7 @@ struct tst_cap {
>  	char *name;
>  };

> -/**
> +/*
>   * TST_CAP() - Create a struct tst_cap entry.

This is the only warning I'd prefer to stay unfixed (i.e. it was kept in the
docs). I wonder if we shouldn't jus rename struct or macro. Because TST_CAP()
should be documented. Cyril @WDYT?

>   *
>   * @action: What should we do, i.e. drop or add capability.
> diff --git a/include/tst_cmd.h b/include/tst_cmd.h
> index 831cb4da486881f9ef345b9f6ead461feb5dfd46..77fbbbc867b6edf841c5347ac612569a5b8470d1 100644
> --- a/include/tst_cmd.h
> +++ b/include/tst_cmd.h
> @@ -19,7 +19,7 @@ enum tst_cmd_flags {
>  	TST_CMD_TCONF_ON_MISSING = 2,
>  };

> -/**
> +/*
>   * struct tst_cmd - Provides details about a command struct needed by LTP test.
>   * @cmd: The name of the command.
>   * @optional: A flag indicating if the command is optional.
> diff --git a/include/tst_kvercmp.h b/include/tst_kvercmp.h
> index 7c991c746a3ab5383535b545c3025f2174d7722b..8457f7926da2022a9fcd215c9404e5cd7f566e0b 100644
> --- a/include/tst_kvercmp.h
> +++ b/include/tst_kvercmp.h
> @@ -93,7 +93,7 @@ struct tst_kern_exv {
>   * @r1: Major kernel version.
>   * @r2: Minor kernel version.
>   * @r3: Kernel patch level.
> - * @vers: A {} terminated array of :ref:`struct tst_kern_exv`.
> + * @vers: A {} terminated array of struct tst_kern_exv.

And ok, C sources and headers should not use :ref:, thanks for fixing it.

Kind regards,
Petr

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

  reply	other threads:[~2026-06-01 14:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  9:52 [LTP] [PATCH 0/4] Fix documentation issues Andrea Cervesato
2026-06-01  9:52 ` [LTP] [PATCH 1/4] doc: Fix broken references and outdated content Andrea Cervesato
2026-06-01 11:58   ` Cyril Hrubis
2026-06-01 13:55   ` Petr Vorel
2026-06-01  9:52 ` [LTP] [PATCH 2/4] doc: Fix typos and grammar Andrea Cervesato
2026-06-01 12:10   ` Cyril Hrubis
2026-06-01 13:57   ` Petr Vorel
2026-06-01  9:52 ` [LTP] [PATCH 3/4] include: Fix kernel-doc warnings in header comments Andrea Cervesato
2026-06-01 14:09   ` Petr Vorel [this message]
2026-06-02  9:04     ` Cyril Hrubis
2026-06-02  9:16       ` Andrea Cervesato via ltp
2026-06-01  9:52 ` [LTP] [PATCH 4/4] doc: Fix incorrect struct tst_test field references Andrea Cervesato
2026-06-01 14:10   ` Petr Vorel
2026-06-02  9:31 ` [LTP] [PATCH 0/4] Fix documentation issues 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=20260601140901.GD3391768@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