All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Erik Schilling" <erik@riscstar.com>
To: "Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Viresh Kumar" <viresh.kumar@linaro.org>,
	"Linus Walleij" <linus.walleij@linaro.org>
Cc: <linux-gpio@vger.kernel.org>,
	"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH libgpiod 09/10] bindings: rust: update rust version
Date: Wed, 13 Aug 2025 08:57:41 +0200	[thread overview]
Message-ID: <DC13RWRXSOVL.4J9R43495IEN@riscstar.com> (raw)
In-Reply-To: <20250812-rust-1-0-0-release-v1-9-372d698f23e8@linaro.org>

On Tue Aug 12, 2025 at 2:10 PM CEST, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> With all previous fixes to rust bindings, we can now update the rust
> version and required edition to 2024.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
>  bindings/rust/libgpiod-sys/Cargo.toml | 4 ++--
>  bindings/rust/libgpiod/Cargo.toml     | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/bindings/rust/libgpiod-sys/Cargo.toml b/bindings/rust/libgpiod-sys/Cargo.toml
> index 7fb5c174ec8186b6ef8cd64e1e6f25a13bd0dcd3..ab86ff8ecf871bfc3f931f8ea08490c4eb40eee6 100644
> --- a/bindings/rust/libgpiod-sys/Cargo.toml
> +++ b/bindings/rust/libgpiod-sys/Cargo.toml
> @@ -9,10 +9,10 @@ authors = ["Viresh Kumar <viresh.kumar@linaro.org>"]
>  description = "libgpiod public header bindings"
>  repository = "https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git"
>  categories = ["external-ffi-bindings", "os::linux-apis"]
> -rust-version = "1.60"
> +rust-version = "1.86"
>  keywords = ["libgpiod", "gpio"]
>  license = "Apache-2.0 OR BSD-3-Clause"
> -edition = "2021"
> +edition = "2024"
>  
>  exclude = [
>      "Makefile.am",

Is there a particular reason to to pick this specific rust-version? This
essentially sets the floor of the MSRV (Minimum Supported Rust Version)
of this lib.

That means that it won't build with any older Rust version, which may
impact users of the lib that are still lagging slightly behind?

I would only bump this if our libs start to require it (or we use new
features ourselves). So I think we should spell out which libs/features
mandate this bump in the commit message and only update as high as we
need to.

- Erik

  reply	other threads:[~2025-08-13  6:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 12:10 [PATCH libgpiod 00/10] bindings: rust: prepare v1.0.0 release Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 01/10] bindings: rust: make Buffer::read_edge_events() lifetimes more explicit Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 02/10] bindings: rust: add missing unsafe block ahead of rust version bump Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 03/10] bindings: rust: update bindgen dependency Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 04/10] bindings: rust: update errno dependency Bartosz Golaszewski
2025-08-13  6:56   ` Erik Schilling
2025-08-13  7:18     ` Bartosz Golaszewski
2025-08-13  8:24       ` Erik Schilling
2025-08-13  8:33         ` Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 05/10] bindings: rust: update cc dependency Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 06/10] bindings: rust: update system-deps dependency Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 07/10] bindings: rust: update thiserror dependency Bartosz Golaszewski
2025-08-12 12:10 ` [PATCH libgpiod 08/10] bindings: rust: update intmap dependency Bartosz Golaszewski
2025-08-13  6:57   ` Erik Schilling
2025-08-13  7:18     ` Bartosz Golaszewski
2025-08-13  8:24       ` Erik Schilling
2025-08-12 12:10 ` [PATCH libgpiod 09/10] bindings: rust: update rust version Bartosz Golaszewski
2025-08-13  6:57   ` Erik Schilling [this message]
2025-08-13  7:12     ` Bartosz Golaszewski
2025-08-13  8:24       ` Erik Schilling
2025-08-12 12:10 ` [PATCH libgpiod 10/10] bindings: rust: update crate versions to v1.0.0 Bartosz Golaszewski
2025-08-13  3:27 ` [PATCH libgpiod 00/10] bindings: rust: prepare v1.0.0 release Viresh Kumar

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=DC13RWRXSOVL.4J9R43495IEN@riscstar.com \
    --to=erik@riscstar.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@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.