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>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Kent Gibson" <warthog618@gmail.com>
Subject: Re: [PATCH libgpiod] bindings: rust: libgpiod-sys: new release
Date: Tue, 21 Nov 2023 15:12:52 +0100 [thread overview]
Message-ID: <CX4JVCLF63WY.1KWBP904270EQ@ablu-work> (raw)
In-Reply-To: <CAMRc=McwQDy_yXpWzMtcF4_A-MaCisdHs9HJF_eJFVz5NKRSYA@mail.gmail.com>
On Tue Nov 21, 2023 at 3:04 PM CET, Bartosz Golaszewski wrote:
> On Tue, Nov 21, 2023 at 9:43 AM Erik Schilling
> <erik.schilling@linaro.org> wrote:
> >
> > During 86860fb ("bindings: rust: libgpiod: release 0.2.2"), I forgot that
> > we also need a libgpiod-sys release in order to expose the new feature
> > flag to raise the minimum libgpiod version.
> >
> > Changelog:
> >
> > 7552e5d (bindings: rust: expose v2.1 features as flag, 2023-11-06)
> > bc91656 (bindings: rust: add wrapper.h to EXTRA_DIST, 2023-11-03)
> > 2e6ee87 (bindings: rust: mention the libgpiod crate from libgpiod-sys, 2023-07-03)
> > d04639d (bindings: rust: bump MSRV to 1.60, 2023-06-16)
> > ebfed6c (bindings: rust: document build without install, 2023-06-12)
> > bce8623 (bindings: rust: exclude Makefile.am from package, 2023-06-12)
> > caabf53 (bindings: rust: add missing license and copyright boilerplate, 2023-06-13)
> >
> > Most changes only touch the build scripts or modify packaging details.
> > Bumping the MSRV and introducing a new feature does not require a major
> > bump.
> >
> > Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
> > ---
>
> Applied, thanks!
Thanks!
Published:
* https://crates.io/crates/libgpiod-sys/versions
* https://crates.io/crates/libgpiod/versions
- Erik
prev parent reply other threads:[~2023-11-21 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 8:43 [PATCH libgpiod] bindings: rust: libgpiod-sys: new release Erik Schilling
2023-11-21 9:04 ` Viresh Kumar
2023-11-21 14:04 ` Bartosz Golaszewski
2023-11-21 14:12 ` 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=CX4JVCLF63WY.1KWBP904270EQ@ablu-work \
--to=erik.schilling@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@gmail.com \
/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