From: Alexander Stein <alexander.stein@mailbox.org>
To: linux-gpio@vger.kernel.org
Cc: Alexander Stein <alexander.stein@mailbox.org>
Subject: [libgpiod] [PATCH 1/5] doc: Fix doxygen warnings
Date: Sat, 8 Aug 2020 11:59:40 +0200 [thread overview]
Message-ID: <20200808095944.188479-2-alexander.stein@mailbox.org> (raw)
In-Reply-To: <20200808095944.188479-1-alexander.stein@mailbox.org>
Apparently __<name>__ is not supported for @defgroup commands. This results
in the following warning (printed multiple time):
gpiod.h:79: warning: group strong: ignoring title ">high_level</strong> High-level
API" that does not match old title ">common</strong> Common helper macros"
Also the module list is broken.
Fix this my removing the underscores.
Signed-off-by: Alexander Stein <alexander.stein@mailbox.org>
---
bindings/cxx/gpiod.hpp | 2 +-
include/gpiod.h | 26 +++++++++++++-------------
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/bindings/cxx/gpiod.hpp b/bindings/cxx/gpiod.hpp
index 5155bdd..59719aa 100644
--- a/bindings/cxx/gpiod.hpp
+++ b/bindings/cxx/gpiod.hpp
@@ -24,7 +24,7 @@ class chip_iter;
struct line_event;
/**
- * @defgroup __gpiod_cxx__ C++ bindings
+ * @defgroup gpiod_cxx C++ bindings
* @{
*/
diff --git a/include/gpiod.h b/include/gpiod.h
index c83ebf7..58de66f 100644
--- a/include/gpiod.h
+++ b/include/gpiod.h
@@ -46,7 +46,7 @@ struct gpiod_line_iter;
struct gpiod_line_bulk;
/**
- * @defgroup __common__ Common helper macros
+ * @defgroup common Common helper macros
* @{
*
* Commonly used utility macros.
@@ -77,7 +77,7 @@ struct gpiod_line_bulk;
/**
* @}
*
- * @defgroup __high_level__ High-level API
+ * @defgroup high_level High-level API
* @{
*
* Simple high-level routines for straightforward GPIO manipulation without
@@ -548,7 +548,7 @@ int gpiod_ctxless_find_line(const char *name, char *chipname,
/**
* @}
*
- * @defgroup __chips__ GPIO chip operations
+ * @defgroup chips GPIO chip operations
* @{
*
* Functions and data structures dealing with GPIO chips.
@@ -691,12 +691,12 @@ int gpiod_chip_find_lines(struct gpiod_chip *chip, const char **names,
/**
* @}
*
- * @defgroup __lines__ GPIO line operations
+ * @defgroup lines GPIO line operations
* @{
*
* Functions and data structures dealing with GPIO lines.
*
- * @defgroup __line_bulk__ Operating on multiple lines
+ * @defgroup line_bulk Operating on multiple lines
* @{
*
* Convenience data structures and helper functions for storing and operating
@@ -807,7 +807,7 @@ gpiod_line_bulk_num_lines(struct gpiod_line_bulk *bulk)
/**
* @}
*
- * @defgroup __line_info__ Line info
+ * @defgroup line_info Line info
* @{
*
* Definitions and functions for retrieving kernel information about both
@@ -955,7 +955,7 @@ gpiod_line_needs_update(struct gpiod_line *line) GPIOD_API GPIOD_DEPRECATED;
/**
* @}
*
- * @defgroup __line_request__ Line requests
+ * @defgroup line_request Line requests
* @{
*
* Interface for requesting GPIO lines from userspace for both values and
@@ -1283,7 +1283,7 @@ bool gpiod_line_is_free(struct gpiod_line *line) GPIOD_API;
/**
* @}
*
- * @defgroup __line_value__ Reading & setting line values
+ * @defgroup line_value Reading & setting line values
* @{
*
* Functions allowing to read and set GPIO line values for single lines and
@@ -1338,7 +1338,7 @@ int gpiod_line_set_value_bulk(struct gpiod_line_bulk *bulk,
/**
* @}
*
- * @defgroup __line_config__ Setting line configuration
+ * @defgroup line_config Setting line configuration
* @{
*
* Functions allowing modification of config options of GPIO lines requested
@@ -1454,7 +1454,7 @@ int gpiod_line_set_direction_output_bulk(struct gpiod_line_bulk *bulk,
/**
* @}
*
- * @defgroup __line_event__ Line events handling
+ * @defgroup line_event Line events handling
* @{
*
* Structures and functions allowing to poll lines for events and read them,
@@ -1568,7 +1568,7 @@ int gpiod_line_event_read_fd_multiple(int fd, struct gpiod_line_event *events,
/**
* @}
*
- * @defgroup __line_misc__ Misc line functions
+ * @defgroup line_misc Misc line functions
* @{
*
* Functions that didn't fit anywhere else.
@@ -1624,7 +1624,7 @@ struct gpiod_chip *gpiod_line_get_chip(struct gpiod_line *line) GPIOD_API;
*
* @}
*
- * @defgroup __iterators__ Iterators for GPIO chips and lines
+ * @defgroup iterators Iterators for GPIO chips and lines
* @{
*
* These functions and data structures allow easy iterating over GPIO
@@ -1748,7 +1748,7 @@ gpiod_line_iter_next(struct gpiod_line_iter *iter) GPIOD_API;
/**
* @}
*
- * @defgroup __misc__ Stuff that didn't fit anywhere else
+ * @defgroup misc Stuff that didn't fit anywhere else
* @{
*
* Various libgpiod-related functions.
--
2.28.0
next prev parent reply other threads:[~2020-08-08 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 9:59 [libgpiod] [PATCH 0/5] Documentation improvements Alexander Stein
2020-08-08 9:59 ` Alexander Stein [this message]
2020-08-08 9:59 ` [libgpiod] [PATCH 2/5] doc: Use autotoolized Doxyfile Alexander Stein
2020-08-13 18:39 ` Bartosz Golaszewski
2020-08-08 9:59 ` [libgpiod] [PATCH 3/5] doc: Fix doxygen warning Alexander Stein
2020-08-08 9:59 ` [libgpiod] [PATCH 4/5] doc: Remove obsolete PERL_PATH Alexander Stein
2020-08-08 9:59 ` [libgpiod] [PATCH 5/5] doc: Add @file to headers Alexander Stein
2020-08-10 16:49 ` [libgpiod] [PATCH 0/5] Documentation improvements Bartosz Golaszewski
2020-08-11 1:39 ` Kent Gibson
2020-08-11 18:24 ` Alexander Stein
2020-08-11 18:59 ` Bartosz Golaszewski
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=20200808095944.188479-2-alexander.stein@mailbox.org \
--to=alexander.stein@mailbox.org \
--cc=linux-gpio@vger.kernel.org \
/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).