Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Bartosz Golaszewski" <brgl@bgdev.pl>
Cc: "Linux-GPIO" <linux-gpio@vger.kernel.org>,
	"Viresh Kumar" <viresh.kumar@linaro.org>
Subject: Re: [libgpiod][PATCH 0/3] thread-safety doc + Rust modeling
Date: Mon, 02 Oct 2023 09:22:32 +0200	[thread overview]
Message-ID: <CVXRTXOO8559.2M83QY2U5MC0K@ablu-work> (raw)
In-Reply-To: <CAMRc=Megx1B+zEqsntLOnJ_dcQngFOy31qr=TMKreefsjX_MAg@mail.gmail.com>

On Mon Oct 2, 2023 at 9:16 AM CEST, Bartosz Golaszewski wrote:
> On Thu, Sep 28, 2023 at 4:37 PM Erik Schilling
> <erik.schilling@linaro.org> wrote:
> >
> > This updates the docs with what was discussed in the linked thread.
> > Then, the Rust bindings are adjusted to match in behaviour.
> >
> > To: Linux-GPIO <linux-gpio@vger.kernel.org>
> > Cc: Bartosz Golaszewski <brgl@bgdev.pl>
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> >
> > Link: https://lore.kernel.org/r/CVHO091CC80Y.3KUOSLSOBVL0T@ablu-work
> > Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
> > ---
> > Erik Schilling (3):
> >       doc: drop unneeded <p> tags
> >       doc: document thread safety guarantees
> >       bindings: rust: mark all owning types as `Send`
> >
> >  bindings/rust/libgpiod/src/edge_event.rs     |  4 ++++
> >  bindings/rust/libgpiod/src/event_buffer.rs   |  8 ++++++++
> >  bindings/rust/libgpiod/src/info_event.rs     |  4 ++++
> >  bindings/rust/libgpiod/src/line_config.rs    |  4 ++++
> >  bindings/rust/libgpiod/src/line_request.rs   |  4 ++++
> >  bindings/rust/libgpiod/src/line_settings.rs  |  4 ++++
> >  bindings/rust/libgpiod/src/request_config.rs |  4 ++++
> >  include/gpiod.h                              | 26 +++++++++++++++++++++++---
> >  8 files changed, 55 insertions(+), 3 deletions(-)
> > ---
> > base-commit: ced90e79217793957b11414f47f8aa8a77c7a2d5
> > change-id: 20230928-rust-send-trait-316a8f31bb97
> >
> > Best regards,
> > --
> > Erik Schilling <erik.schilling@linaro.org>
> >
>
> Series applied, thanks!

Thanks for merging and the clarifications!

- Erik


      reply	other threads:[~2023-10-02  7:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 14:37 [libgpiod][PATCH 0/3] thread-safety doc + Rust modeling Erik Schilling
2023-09-28 14:37 ` [libgpiod][PATCH 1/3] doc: drop unneeded <p> tags Erik Schilling
2023-09-28 14:37 ` [libgpiod][PATCH 2/3] doc: document thread safety guarantees Erik Schilling
2023-09-28 14:37 ` [libgpiod][PATCH 3/3] bindings: rust: mark all owning types as `Send` Erik Schilling
2023-09-29 10:58   ` Viresh Kumar
2023-09-29 12:45     ` Bartosz Golaszewski
2023-09-29 12:47       ` Erik Schilling
2023-09-29 13:07         ` Bartosz Golaszewski
2023-10-02  7:16 ` [libgpiod][PATCH 0/3] thread-safety doc + Rust modeling Bartosz Golaszewski
2023-10-02  7:22   ` Erik Schilling [this message]

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=CVXRTXOO8559.2M83QY2U5MC0K@ablu-work \
    --to=erik.schilling@linaro.org \
    --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