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 <hansg@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, brgl@kernel.org
Subject: Re: [PATCH v2] platform/x86: barco-p50-gpio: attach software node to its target GPIO device
Date: Fri, 08 May 2026 21:15:09 +0300 [thread overview]
Message-ID: <177826410949.8043.11494785633688307149.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260427102459.110332-1-bartosz.golaszewski@oss.qualcomm.com>
On Mon, 27 Apr 2026 12:24:58 +0200, Bartosz Golaszewski wrote:
> The software node representing the GPIO controller to consumers is
> "dangling": it's not really attached to the device. The GPIO lookup
> relies on matching the name of the node to the chip's label. Switch to
> using platform_device_register_full() and use the swnode field of struct
> platform_device_info to attach the software node to the GPIO device.
>
>
> [...]
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: attach software node to its target GPIO device
commit: 49133d4ae0c9ceb63fa042c0b46b34e26e1c6676
--
i.
parent reply other threads:[~2026-05-08 18:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260427102459.110332-1-bartosz.golaszewski@oss.qualcomm.com>]
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=177826410949.8043.11494785633688307149.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.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