From: Erik Schilling <erik.schilling@linaro.org>
To: Linux-GPIO <linux-gpio@vger.kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Erik Schilling <erik.schilling@linaro.org>
Subject: [libgpiod][PATCH v2 2/2] bindings: rust: mention the libgpiod crate from libgpiod-sys
Date: Mon, 03 Jul 2023 09:20:00 +0200 [thread overview]
Message-ID: <20230703-rust-readme-v2-2-ba7d7f04bed6@linaro.org> (raw)
In-Reply-To: <20230703-rust-readme-v2-0-ba7d7f04bed6@linaro.org>
If people view this README.md on crates.io [1], they likely want to
use the safe wrapper instead. So this hints the existence of that other
crate.
[1] https://crates.io/crates/libgpiod-sys
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
---
bindings/rust/libgpiod-sys/README.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/bindings/rust/libgpiod-sys/README.md b/bindings/rust/libgpiod-sys/README.md
index f9db496..05acd9e 100644
--- a/bindings/rust/libgpiod-sys/README.md
+++ b/bindings/rust/libgpiod-sys/README.md
@@ -8,6 +8,9 @@ SPDX-FileCopyrightText: 2022 Viresh Kumar <viresh.kumar@linaro.org>
Automatically generated Rust FFI bindings via
[bindgen](https://github.com/rust-lang/rust-bindgen).
+Typically, you will want to use the safe `libgpiod` wrapper crate instead of
+these unsafe wrappers around the C lib.
+
## Build requirements
A compatible variant of the C library needs to detectable using pkg-config.
--
2.41.0
next prev parent reply other threads:[~2023-07-03 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:19 [libgpiod][PATCH v2 0/2] bindings: rust: add README for crates.io Erik Schilling
2023-07-03 7:19 ` [libgpiod][PATCH v2 1/2] bindings: rust: add README.md for libgpiod crate Erik Schilling
2023-07-03 7:20 ` Erik Schilling [this message]
2023-07-03 7:22 ` [libgpiod][PATCH v2 0/2] bindings: rust: add README for crates.io Viresh Kumar
2023-07-03 10:48 ` 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=20230703-rust-readme-v2-2-ba7d7f04bed6@linaro.org \
--to=erik.schilling@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=viresh.kumar@linaro.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).