From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <metan@ucw.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] include: doc: Convert comments into linuxdoc
Date: Mon, 25 Mar 2024 13:34:19 +0100 [thread overview]
Message-ID: <20240325123419.GC627989@pevik> (raw)
In-Reply-To: <20240322120700.3072-2-metan@ucw.cz>
Hi Cyril,
generally LGTM, not looking deeply as you plan to send v2.
Do you plan later to work also on include/tst_test_macros.h?
Do you need any help on docs?
Also I should find time to study how to generate docs locally.
...
> /**
> - * Add, check or remove a capabilities
> + * tst_cap_setup() - Add, check or remove a capabilities.
> + *
> + * @cap: An {} terminated array of capabilities to alter.
> + * @action_mask: Decides which actions are done, i.e. only drop caps, add them
> + * or both.
> *
> * Takes a NULL terminated array of structs which describe whether some
> * capabilities are needed or not and mask that determines subset of the
> * actions to be performed. Loops over the array and if mask matches the
> * element action it's passed to tst_cap_action().
> */
> -void tst_cap_setup(struct tst_cap *cap, unsigned int action_mask);
> +void tst_cap_setup(struct tst_cap *cap, enum tst_cap_act action_mask);
This is a real code change, which could be merged separately on the docs change.
But I see whole patchset is not only about docs, but about moving definitions
into enums thus OK for me.
> #endif /* TST_CAPABILITY_H */
> diff --git a/include/tst_checkpoint.h b/include/tst_checkpoint.h
> index 1b6911d73..62d87d60b 100644
> --- a/include/tst_checkpoint.h
> +++ b/include/tst_checkpoint.h
> @@ -1,24 +1,86 @@
> -/* SPDX-License-Identifier: GPL-2.0-or-later
> +// SPDX-License-Identifier: GPL-2.0-or-later
I guess this change will cause checkpatch.pl to complain:
tst_checkpoint.h:1: WARNING: Improper SPDX comment style for 'tst_checkpoint.h', please use '/*' instead
tst_checkpoint.h:1: WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
Generally LGTM.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-03-25 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 12:06 [LTP] [PATCH 0/1] doc: Add generated API docs Cyril Hrubis
2024-03-22 12:07 ` [LTP] [PATCH 1/1] include: doc: Convert comments into linuxdoc Cyril Hrubis
2024-03-25 12:34 ` Petr Vorel [this message]
2024-03-25 12:53 ` Cyril Hrubis
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=20240325123419.GC627989@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=metan@ucw.cz \
/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