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 v2 9/9] include: Fix API comment spelling and style
Date: Fri, 11 Sep 2026 14:21:15 +0200 [thread overview]
Message-ID: <20260911122115.GF1454430@pevik> (raw)
In-Reply-To: <20260911-fix_documentation-v2-9-716b2613c477@suse.com>
Hi Andrea,
> /**
> - * tse_nodemap_count_pages() - Check which numa node resides each page.
> + * tse_nodemap_count_pages() - Check on which NUMA node each page resides.
> *
> * Check on which numa node resides each page of the mapping starting at ptr
> * and continuing pages long and increases nodemap counters accordingly.
> @@ -114,7 +114,7 @@ enum tse_numa_types {
> * requested amount of free+buffers memory it's not included in
> * the resulting list of nodes.
> *
> - * return: On success returns allocated and initialized struct tse_nodemap which contains
> + * Return: On success returns allocated and initialized struct tse_nodemap which contains
> * array of numa node ids that contains desired resources.
Although lowercase 'r' on return also works as expected (but it's indeed better
to unify), again: whitespace on the second line breaks formatting (first line is
bold, second line is shifted.
Unfortunately Return: does not work like struct members, which allow shifting
without any formatting (OTOH other formating e.g. lists does not work on them).
The rest hopefully LGTM.
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Thanks for whole patchset.
Kind regards,
Petr
diff --git include/tse_numa.h include/tse_numa.h
index add048eb4c..ac6aab41b8 100644
--- include/tse_numa.h
+++ include/tse_numa.h
@@ -114,8 +114,8 @@ enum tse_numa_types {
* requested amount of free+buffers memory it's not included in
* the resulting list of nodes.
*
- * Return: On success returns allocated and initialized struct tse_nodemap which contains
- * array of numa node ids that contains desired resources.
+ * Return: On success returns allocated and initialized struct tse_nodemap which
+ * contains array of numa node ids that contains desired resources.
*/
struct tse_nodemap *tse_get_nodemap(int type, size_t min_mem_kb);
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-11 12:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 7:04 [LTP] [PATCH v2 0/9] doc: Improve and fix documentation and API comments Andrea Cervesato
2026-09-11 7:04 ` [LTP] [PATCH v2 1/9] doc: Fix examples and generated links Andrea Cervesato
2026-09-11 7:04 ` [LTP] [PATCH v2 2/9] doc: Correct guide and API descriptions Andrea Cervesato
2026-09-11 10:59 ` Petr Vorel
2026-09-11 7:04 ` [LTP] [PATCH v2 3/9] doc: Clarify API coverage and navigation Andrea Cervesato
2026-09-11 7:04 ` [LTP] [PATCH v2 4/9] include: Document assertion API macros Andrea Cervesato
2026-09-11 11:10 ` Petr Vorel
2026-09-11 7:04 ` [LTP] [PATCH v2 5/9] include: Document filesystem test utilities Andrea Cervesato
2026-09-11 11:19 ` Petr Vorel
2026-09-11 7:04 ` [LTP] [PATCH v2 6/9] include: Document memory " Andrea Cervesato
2026-09-11 11:39 ` Petr Vorel
2026-09-11 7:04 ` [LTP] [PATCH v2 7/9] include: Document safe file operations Andrea Cervesato
2026-09-11 7:04 ` [LTP] [PATCH v2 8/9] doc: Document CPU and common test helpers Andrea Cervesato
2026-09-11 11:56 ` Petr Vorel
2026-09-11 7:04 ` [LTP] [PATCH v2 9/9] include: Fix API comment spelling and style Andrea Cervesato
2026-09-11 12:21 ` Petr Vorel [this message]
2026-09-11 12:34 ` [LTP] [PATCH v2 0/9] doc: Improve and fix documentation and API comments Andrea Cervesato via ltp
2026-09-11 13:06 ` 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=20260911122115.GF1454430@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