From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Santosh Kumar Yadav <santoshkumar.yadav@barco.com>,
Hans de Goede <hansg@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Peter Korsgaard <peter.korsgaard@barco.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: barco-p50-gpio: use software nodes for gpio-leds/keys
Date: Wed, 24 Sep 2025 15:58:09 +0300 [thread overview]
Message-ID: <175871868912.14395.3763768947038329370.b4-ty@linux.intel.com> (raw)
In-Reply-To: <2meuzip4qnxvle4bwk4hbow4j34ii3cwb46xd5inq5btif5mjg@iiygy6ir7vtr>
On Sun, 10 Aug 2025 21:31:37 -0700, Dmitry Torokhov wrote:
> In preparation of dropping support for legacy GPIO API from gpio-keys
> switch the driver to use software nodes/properties to describe
> GPIO-connected LED and button.
>
>
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/1] platform/x86: barco-p50-gpio: use software nodes for gpio-leds/keys
commit: ff289dc249fd7699081494bd70a91b5718d27114
--
i.
prev parent reply other threads:[~2025-09-24 12:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 4:31 [PATCH] platform/x86: barco-p50-gpio: use software nodes for gpio-leds/keys Dmitry Torokhov
2025-08-11 12:44 ` Andy Shevchenko
2025-08-11 14:20 ` Hans de Goede
2025-08-11 15:45 ` Andy Shevchenko
2025-08-11 15:49 ` Dmitry Torokhov
2025-08-11 16:01 ` Andy Shevchenko
2025-08-11 16:11 ` Dmitry Torokhov
2025-08-11 17:40 ` Hans de Goede
2025-08-11 17:44 ` Hans de Goede
2025-08-11 17:59 ` Dmitry Torokhov
2025-08-12 9:47 ` Hans de Goede
2025-09-08 12:48 ` Ilpo Järvinen
2025-09-10 10:56 ` Hans de Goede
2025-08-11 19:58 ` Andy Shevchenko
2025-09-24 12:58 ` 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=175871868912.14395.3763768947038329370.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hansg@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