From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Erik Schilling" <erik.schilling@linaro.org>,
"Linux-GPIO" <linux-gpio@vger.kernel.org>
Cc: "Viresh Kumar" <viresh.kumar@linaro.org>
Subject: Re: [libgpiod][PATCH 0/2] rust: bindings: drop unneeded Arc within Chip
Date: Wed, 27 Sep 2023 11:31:31 +0200 [thread overview]
Message-ID: <CVTLFYVADV33.3DM00E8O1IER4@ablu-work> (raw)
In-Reply-To: <20230927-chip-drop-arc-v1-0-28013bf95948@linaro.org>
Got the prefixes inverted in the subject of the cover-letter... Correct
in the patches though. Will fix if I need a v2.
On Wed Sep 27, 2023 at 11:25 AM CEST, Erik Schilling wrote:
> While reviewing code for thread-safety. I realized that this structure
> was a bit more complex than it should be...
>
> To: Linux-GPIO <linux-gpio@vger.kernel.org>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
>
> Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
> ---
> Erik Schilling (2):
> bindings: rust: construct chip infos by reference
> bindings: rust: drop unneeded Arc within Chip
>
> bindings/rust/libgpiod/src/chip.rs | 83 +++++++++++++++-----------------------
> 1 file changed, 33 insertions(+), 50 deletions(-)
> ---
> base-commit: ced90e79217793957b11414f47f8aa8a77c7a2d5
> change-id: 20230927-chip-drop-arc-57debbe1e52a
>
> Best regards,
next prev parent reply other threads:[~2023-09-27 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 9:25 [libgpiod][PATCH 0/2] rust: bindings: drop unneeded Arc within Chip Erik Schilling
2023-09-27 9:25 ` [libgpiod][PATCH 1/2] bindings: rust: construct chip infos by reference Erik Schilling
2023-09-27 9:25 ` [libgpiod][PATCH 2/2] bindings: rust: drop unneeded Arc within Chip Erik Schilling
2023-09-27 9:31 ` Erik Schilling [this message]
2023-09-28 8:58 ` [libgpiod][PATCH 0/2] rust: bindings: " Viresh Kumar
2023-09-29 12:41 ` 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=CVTLFYVADV33.3DM00E8O1IER4@ablu-work \
--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 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.