All of lore.kernel.org
 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 1/9] doc: Fix examples and generated links
Date: Thu, 10 Sep 2026 21:07:13 +0200	[thread overview]
Message-ID: <20260910190713.GA255237@pevik> (raw)
In-Reply-To: <20260910-fix_documentation-v1-1-44313069bbe8@suse.com>

Hi Andrea,

Good catches, thanks!

Reviewed-by: Petr Vorel <pvorel@suse.cz>

...
>          'inotify_add_watch': f'{ltp_syscalls_path}/inotify',
>          'inotify_init': f'{ltp_syscalls_path}/inotify',
>          'inotify_rm_watch': f'{ltp_syscalls_path}/inotify',
> @@ -293,7 +293,7 @@ def _generate_tags_table(tags):
>          "linux-git": "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=",
>          "linux-stable-git": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=",
>          "glibc-git": "https://sourceware.org/git/?p=glibc.git;a=commit;h=",
> -        "musl-git": "https://git.musl-libc.org/cgit/musl/commit/src/linux/clone.c?id=",
> +        "musl-git": "https://git.musl-libc.org/cgit/musl/commit/?id=",
Interestingly, the old link also works (cgit v1.2.1 apparently ignores any path
after /commit/ when there is id parameter), but it's of course good to fix it.

>          "CVE": cve_url + 'CVE-',
>      }

> diff --git a/doc/developers/api_shell_tests.rst b/doc/developers/api_shell_tests.rst
> index 937ffee2e..22cab6803 100644
> --- a/doc/developers/api_shell_tests.rst
> +++ b/doc/developers/api_shell_tests.rst
> @@ -41,10 +41,11 @@ when it's empty.
>     #  "needs_root": true,
>     #  "needs_tmpdir": true,
>     #  "needs_kconfigs": ["CONFIG_NUMA=y"],
> -   #  "tags": {
> +   #  "tags": [
>     #   ["linux-git", "432fd03240fa"]
Could you, please, change  before merge this line to:
      #   ["linux-git", "cf01fb9985e8deb25ccf0ea54d916b8871ae0e62"]

(1) longer hash 2) hash which actually exists in kernel tree.)
thanks!

Kind regards,
Petr

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

  parent reply	other threads:[~2026-09-10 19:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  8:33 [LTP] [PATCH 0/9] doc: Improve and fix documentation and API comments Andrea Cervesato
2026-09-10  8:33 ` [LTP] [PATCH 1/9] doc: Fix examples and generated links Andrea Cervesato
2026-09-10 10:47   ` [LTP] " linuxtestproject.agent
2026-09-10 19:07   ` Petr Vorel [this message]
2026-09-10  8:33 ` [LTP] [PATCH 2/9] doc: Correct guide and API descriptions Andrea Cervesato
2026-09-10 19:32   ` Petr Vorel
2026-09-10  8:33 ` [LTP] [PATCH 3/9] doc: Clarify API coverage and navigation Andrea Cervesato
2026-09-10 19:52   ` Petr Vorel
2026-09-11  6:57     ` Andrea Cervesato via ltp
2026-09-10  8:33 ` [LTP] [PATCH 4/9] include: Document assertion API macros Andrea Cervesato
2026-09-10  8:33 ` [LTP] [PATCH 5/9] include: Document filesystem test utilities Andrea Cervesato
2026-09-10  8:33 ` [LTP] [PATCH 6/9] include: Document memory " Andrea Cervesato
2026-09-10  8:33 ` [LTP] [PATCH 7/9] include: Document safe file operations Andrea Cervesato
2026-09-10  8:33 ` [LTP] [PATCH 8/9] doc: Document CPU and common test helpers Andrea Cervesato
2026-09-10  8:33 ` [LTP] [PATCH 9/9] include: Fix API comment spelling and style Andrea Cervesato

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=20260910190713.GA255237@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 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.