From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Santosh Kumar Yadav <santoshkumar.yadav@barco.com>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Hans de Goede <hdegoede@redhat.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 0/3] platform/x86: convert GPIO chips to using new value setters
Date: Fri, 11 Apr 2025 15:24:11 +0300 [thread overview]
Message-ID: <174437425146.3859.1859602845128430744.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250408-gpiochip-set-rv-platform-x86-v1-0-6f67e76a722c@linaro.org>
On Tue, 08 Apr 2025 09:19:52 +0200, Bartosz Golaszewski wrote:
> struct gpio_chip now has callbacks for setting line values that return
> an integer, allowing to indicate failures. We're in the process of
> converting all GPIO drivers to using the new API. This series converts
> all the x86 platform GPIO controllers.
>
>
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/3] platform/x86: barco-p50: use new GPIO line value setter callbacks
commit: 29ba3b6037dcf73f0fc563611ea81669fb2a3f37
[2/3] platform/x86: int0002: use new GPIO line value setter callbacks
commit: e0071ad2ee0bf09a06e650cb5d697e6c8a7ca827
[3/3] platform/x86: silicom: use new GPIO line value setter callbacks
commit: 88f67f2a99f061cb938812db3deb965504cf5c5c
--
i.
prev parent reply other threads:[~2025-04-11 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 7:19 Bartosz Golaszewski
2025-04-08 7:19 ` [PATCH 1/3] platform/x86: barco-p50: use new GPIO line value setter callbacks Bartosz Golaszewski
2025-04-08 7:24 ` Korsgaard, Peter
2025-04-08 7:19 ` [PATCH 2/3] platform/x86: int0002: " Bartosz Golaszewski
2025-04-08 7:19 ` [PATCH 3/3] platform/x86: silicom: " Bartosz Golaszewski
2025-04-08 8:50 ` [PATCH 0/3] platform/x86: convert GPIO chips to using new value setters Hans de Goede
2025-04-11 12:24 ` Ilpo Järvinen [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=174437425146.3859.1859602845128430744.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.korsgaard@barco.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=santoshkumar.yadav@barco.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
all inboxes | Powered by JetHome®