From: Lee Jones <lee@kernel.org>
To: Lee Jones <lee@kernel.org>, Daniel Thompson <danielt@kernel.org>,
Jingoo Han <jingoohan1@gmail.com>, Helge Deller <deller@gmx.de>,
Tony Lindgren <tony@atomide.com>, Pavel Machek <pavel@ucw.cz>,
Jean-Jacques Hiblot <jjhiblot@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "Saravana Kannan" <saravanak@google.com>,
"Hervé Codina" <herve.codina@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Daniel Thompson" <daniel.thompson@linaro.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Alexander Sverdlin" <alexander.sverdlin@gmail.com>
Subject: Re: (subset) [PATCH v6] backlight: led-backlight: add devlink to supplier LEDs
Date: Thu, 06 Nov 2025 17:00:41 +0000 [thread overview]
Message-ID: <176244844196.1963389.1499748337381220684.b4-ty@kernel.org> (raw)
In-Reply-To: <20250519-led-backlight-add-devlink-to-supplier-class-device-v6-1-845224aeb2ce@bootlin.com>
On Mon, 19 May 2025 22:19:11 +0200, Luca Ceresoli wrote:
> led-backlight is a consumer of one or multiple LED class devices, but
> devlink is currently unable to create correct supplier-producer links when
> the supplier is a class device. It creates instead a link where the
> supplier is the parent of the expected device.
>
> One consequence is that removal order is not correctly enforced.
>
> [...]
Applied, thanks!
[1/1] backlight: led-backlight: add devlink to supplier LEDs
commit: 67d8eed26eadb1edd4873d24889be26aa9b73fe5
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-11-06 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 20:19 [PATCH v6] backlight: led-backlight: add devlink to supplier LEDs Luca Ceresoli
2025-05-20 6:05 ` Herve Codina
2025-10-23 12:41 ` Sverdlin, Alexander
2025-10-29 17:45 ` Daniel Thompson
2025-10-30 12:54 ` Luca Ceresoli
2025-11-06 17:00 ` Lee Jones [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=176244844196.1963389.1499748337381220684.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=alexander.sverdlin@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=danielt@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=herve.codina@bootlin.com \
--cc=jingoohan1@gmail.com \
--cc=jjhiblot@ti.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=pavel@ucw.cz \
--cc=saravanak@google.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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