From: Kent Gibson <warthog618@gmail.com>
To: linux-gpio@vger.kernel.org, brgl@bgdev.pl
Cc: Kent Gibson <warthog618@gmail.com>
Subject: [libgpiod][PATCH 3/4] cxx: examples: file comment consistency
Date: Sat, 24 Jun 2023 13:20:53 +0800 [thread overview]
Message-ID: <20230624052054.13206-4-warthog618@gmail.com> (raw)
In-Reply-To: <20230624052054.13206-1-warthog618@gmail.com>
Make the file comment for reconfigure_input_to_output consistent with
other language examples.
Signed-off-by: Kent Gibson <warthog618@gmail.com>
---
bindings/cxx/examples/reconfigure_input_to_output.cpp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/bindings/cxx/examples/reconfigure_input_to_output.cpp b/bindings/cxx/examples/reconfigure_input_to_output.cpp
index 7b52dab..896c812 100644
--- a/bindings/cxx/examples/reconfigure_input_to_output.cpp
+++ b/bindings/cxx/examples/reconfigure_input_to_output.cpp
@@ -2,8 +2,8 @@
// SPDX-FileCopyrightText: 2023 Kent Gibson <warthog618@gmail.com>
/*
- * Minimal example of requesting a line intended for bi-directional use as
- * input and then switching to output.
+ * Example of a bi-directional line requested as input and then switched
+ * to output.
*/
#include <cstdlib>
--
2.41.0
next prev parent reply other threads:[~2023-06-24 5:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 5:20 [libgpiod][PATCH 0/4] python examples and comment corrections Kent Gibson
2023-06-24 5:20 ` [libgpiod][PATCH 1/4] bindings: python: examples: replace tools examples with use case examples Kent Gibson
2023-06-26 8:02 ` Bartosz Golaszewski
2023-06-26 8:18 ` Kent Gibson
2023-06-26 8:24 ` Bartosz Golaszewski
2023-06-24 5:20 ` [libgpiod][PATCH 2/4] core: examples: fix file comments Kent Gibson
2023-06-26 8:07 ` Bartosz Golaszewski
2023-06-24 5:20 ` Kent Gibson [this message]
2023-06-24 5:20 ` [libgpiod][PATCH 4/4] rust: examples: file comment consistency Kent Gibson
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=20230624052054.13206-4-warthog618@gmail.com \
--to=warthog618@gmail.com \
--cc=brgl@bgdev.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.