From: Erik Wierich <erik@riscstar.com>
To: Linux-GPIO <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: Erik Wierich <erik@riscstar.com>
Subject: [PATCH libgpiod 0/2] bindings: rust: mark raw constructors as unsafe + rename to `from_raw`
Date: Mon, 21 Jul 2025 09:41:52 +0200 [thread overview]
Message-ID: <20250721-rust-unsafe-consistency-v1-0-aa1b42ed5983@riscstar.com> (raw)
This is based on top of:
https://lore.kernel.org/linux-gpio/20250720-new-with-settings-crate-v1-1-a51392bd5b13@linaro.org/
Signed-off-by: Erik Wierich <erik@riscstar.com>
---
Erik Wierich (2):
bindings: rust: mark constructors that take raw pointers unsafe
bindings: rust: rename constructors that wrap raw objects to `from_raw`
bindings/rust/libgpiod/src/chip.rs | 10 ++++++++--
bindings/rust/libgpiod/src/info_event.rs | 7 ++++++-
bindings/rust/libgpiod/src/line_config.rs | 7 ++++++-
bindings/rust/libgpiod/src/line_request.rs | 7 ++++++-
bindings/rust/libgpiod/src/line_settings.rs | 10 +++++++++-
5 files changed, 35 insertions(+), 6 deletions(-)
---
base-commit: ec1a9986dce755a96780e1c9c3a3b1b0227061bc
change-id: 20250721-rust-unsafe-consistency-be78ed4f98a9
Best regards,
--
Erik Wierich <erik@riscstar.com>
next reply other threads:[~2025-07-21 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 7:41 Erik Wierich [this message]
2025-07-21 7:41 ` [PATCH libgpiod 1/2] bindings: rust: mark constructors that take raw pointers unsafe Erik Wierich
2025-07-21 7:41 ` [PATCH libgpiod 2/2] bindings: rust: rename constructors that wrap raw objects to `from_raw` Erik Wierich
2025-07-21 7:48 ` [PATCH libgpiod 0/2] bindings: rust: mark raw constructors as unsafe + rename " Viresh Kumar
2025-07-21 13:20 ` 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=20250721-rust-unsafe-consistency-v1-0-aa1b42ed5983@riscstar.com \
--to=erik@riscstar.com \
--cc=brgl@bgdev.pl \
--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).