From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 03/10] Add listmount01 test
Date: Thu, 16 May 2024 03:47:27 +0200 [thread overview]
Message-ID: <20240516014727.GA276881@pevik> (raw)
In-Reply-To: <20240515113338.554-4-andrea.cervesato@suse.de>
Hi Andrea,
...
> +++ b/testcases/kernel/syscalls/listmount/listmount01.c
> @@ -0,0 +1,66 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2024 SUSE LLC Andrea Cervesato <andrea.cervesato@suse.com>
> + */
> +
> +/**
This is for kerneldoc, but for docparse it must be: /*\
Your version causes that the description is not in the documentation.
The same applies for whole source.
BTW it's worth to run the doc generation locally.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-05-16 1:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 11:33 [LTP] [PATCH v1 00/10] statmount/listmount testing suites Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 01/10] Add SAFE_STATX macro Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 02/10] Add listmount/statmount fallback declarations Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 03/10] Add listmount01 test Andrea Cervesato
2024-05-16 1:47 ` Petr Vorel [this message]
2024-05-15 11:33 ` [LTP] [PATCH v2 04/10] Add listmount02 test Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 05/10] Add stamount01 test Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 06/10] Add statmount02 test Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 07/10] Add statmount03 test Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 08/10] Add statmount04 test Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 09/10] Add statmount05 test Andrea Cervesato
2024-05-15 11:33 ` [LTP] [PATCH v2 10/10] Add statmount06 test 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=20240516014727.GA276881@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