From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>, Will Cohen <wwcohen@gmail.com>,
Keno Fischer <keno@juliacomputing.com>,
Michael Roitzsch <reactorcontrol@icloud.com>,
Fabian Franz <fabianfranz.oss@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PULL v2 19/19] fsdev/p9array.h: convert Doxygen -> kerneldoc format
Date: Mon, 07 Mar 2022 12:15:00 +0100 [thread overview]
Message-ID: <35b6466459f9234b9cb30296f243a70b6f1b44b7.1646651700.git.qemu_oss@crudebyte.com> (raw)
In-Reply-To: <cover.1646651700.git.qemu_oss@crudebyte.com>
API doc comments in QEMU are supposed to be in kerneldoc format, so
convert API doc comments from Doxygen format to kerneldoc format.
Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
Reviewed-by: Greg Kurz <groug@kaod.org>
Message-Id: <2e2d46a402560f155de322d95789ba107d728885.1646314856.git.qemu_oss@crudebyte.com>
---
fsdev/p9array.h | 38 +++++++++++++++++++++-----------------
1 file changed, 21 insertions(+), 17 deletions(-)
diff --git a/fsdev/p9array.h b/fsdev/p9array.h
index 6aa25327ca..90e83a7c7b 100644
--- a/fsdev/p9array.h
+++ b/fsdev/p9array.h
@@ -81,11 +81,11 @@
*/
/**
- * Declares an array type for the passed @a scalar_type.
+ * P9ARRAY_DECLARE_TYPE() - Declares an array type for the passed @scalar_type.
*
- * This is typically used from a shared header file.
+ * @scalar_type: type of the individual array elements
*
- * @param scalar_type - type of the individual array elements
+ * This is typically used from a shared header file.
*/
#define P9ARRAY_DECLARE_TYPE(scalar_type) \
typedef struct P9Array##scalar_type { \
@@ -97,14 +97,14 @@
void p9array_auto_free_##scalar_type(scalar_type **auto_var); \
/**
- * Defines an array type for the passed @a scalar_type and appropriate
- * @a scalar_cleanup_func.
+ * P9ARRAY_DEFINE_TYPE() - Defines an array type for the passed @scalar_type
+ * and appropriate @scalar_cleanup_func.
*
- * This is typically used from a C unit file.
+ * @scalar_type: type of the individual array elements
+ * @scalar_cleanup_func: appropriate function to free memory dynamically
+ * allocated by individual array elements before
*
- * @param scalar_type - type of the individual array elements
- * @param scalar_cleanup_func - appropriate function to free memory dynamically
- * allocated by individual array elements before
+ * This is typically used from a C unit file.
*/
#define P9ARRAY_DEFINE_TYPE(scalar_type, scalar_cleanup_func) \
void p9array_new_##scalar_type(scalar_type **auto_var, size_t len) \
@@ -132,23 +132,27 @@
} \
/**
+ * P9ARRAY_REF() - Declare a reference variable for an array.
+ *
+ * @scalar_type: type of the individual array elements
+ *
* Used to declare a reference variable (unique pointer) for an array. After
* leaving the scope of the reference variable, the associated array is
* automatically freed.
- *
- * @param scalar_type - type of the individual array elements
*/
#define P9ARRAY_REF(scalar_type) \
__attribute((__cleanup__(p9array_auto_free_##scalar_type))) scalar_type*
/**
- * Allocates a new array of passed @a scalar_type with @a len number of array
- * elements and assigns the created array to the reference variable
- * @a auto_var.
+ * P9ARRAY_NEW() - Allocate a new array.
*
- * @param scalar_type - type of the individual array elements
- * @param auto_var - destination reference variable
- * @param len - amount of array elements to be allocated immediately
+ * @scalar_type: type of the individual array elements
+ * @auto_var: destination reference variable
+ * @len: amount of array elements to be allocated immediately
+ *
+ * Allocates a new array of passed @scalar_type with @len number of array
+ * elements and assigns the created array to the reference variable
+ * @auto_var.
*/
#define P9ARRAY_NEW(scalar_type, auto_var, len) \
QEMU_BUILD_BUG_MSG( \
--
2.20.1
next prev parent reply other threads:[~2022-03-07 11:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 11:15 [PULL v2 00/19] 9p queue 2022-03-07 (previous 2022-03-04) Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 14/19] 9pfs/9p.h: convert Doxygen -> kerneldoc format Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 09/19] 9p: darwin: Implement compatibility for mknodat Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 10/19] 9p: darwin: Adjust assumption on virtio-9p-test Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 05/19] 9p: darwin: Ignore O_{NOATIME, DIRECT} Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 18/19] 9pfs/coth.h: drop Doxygen format on v9fs_co_run_in_worker() Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 06/19] 9p: darwin: Move XATTR_SIZE_MAX->P9_XATTR_SIZE_MAX Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 03/19] 9p: darwin: Handle struct stat(fs) differences Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 11/19] 9p: darwin: meson: Allow VirtFS on Darwin Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 16/19] 9pfs/9p.c: convert Doxygen -> kerneldoc format Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 08/19] 9p: darwin: Compatibility for f/l*xattr Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 04/19] 9p: darwin: Handle struct dirent differences Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 02/19] 9p: Rename 9p-util -> 9p-util-linux Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 12/19] 9pfs: move qemu_dirent_dup() from osdep -> 9p-util Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 17/19] 9pfs/9p-util.h: convert Doxygen -> kerneldoc format Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 13/19] 9pfs: drop Doxygen format from qemu_dirent_dup() API comment Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 07/19] 9p: darwin: *xattr_nofollow implementations Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 01/19] 9p: linux: Fix a couple Linux assumptions Christian Schoenebeck
2022-03-07 11:15 ` [PULL v2 15/19] 9pfs/codir.c: convert Doxygen -> kerneldoc format Christian Schoenebeck
2022-03-07 11:15 ` Christian Schoenebeck [this message]
2022-03-08 12:37 ` [PULL v2 00/19] 9p queue 2022-03-07 (previous 2022-03-04) Peter Maydell
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=35b6466459f9234b9cb30296f243a70b6f1b44b7.1646651700.git.qemu_oss@crudebyte.com \
--to=qemu_oss@crudebyte.com \
--cc=fabianfranz.oss@gmail.com \
--cc=groug@kaod.org \
--cc=keno@juliacomputing.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=reactorcontrol@icloud.com \
--cc=wwcohen@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).