From: sashiko-bot@kernel.org
To: "Josef Schlehofer" <pepe.schlehofer@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, lee@kernel.org,
linux-leds@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: leds: Add CZ.NIC Turris 1.x LED controller
Date: Mon, 28 Sep 2026 11:23:41 +0000 [thread overview]
Message-ID: <20260928112342.2B4471F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260928111907.72592-2-pepe.schlehofer@gmail.com>
> From: Pali Rohár <pali@kernel.org>
>
> Add a binding for the LED controller on the front panel of the CZ.NIC
> Turris 1.x routers. The LEDs are controlled by the firmware of the
> CZ.NIC CPLD, which is memory mapped on the local bus.
>
> The turris1x.dts device tree, which is part of the mainline kernel since
> v6.0, already references this compatible string.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
> Cc: Marek Behún <kabel@kernel.org>
> Co-developed-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
> Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260928111907.72592-1-pepe.schlehofer@gmail.com?part=1
next prev parent reply other threads:[~2026-09-28 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 11:19 [PATCH v3 0/2] leds: Add support for CZ.NIC Turris 1.x LEDs Josef Schlehofer
2026-09-28 11:19 ` [PATCH v3 1/2] dt-bindings: leds: Add CZ.NIC Turris 1.x LED controller Josef Schlehofer
2026-09-28 11:23 ` sashiko-bot [this message]
2026-10-07 21:06 ` Rob Herring (Arm)
2026-09-28 11:19 ` [PATCH v3 2/2] leds: Add support for Turris 1.x LEDs Josef Schlehofer
2026-09-28 11:34 ` sashiko-bot
2026-09-28 13:07 ` Andy Shevchenko
2026-09-29 14:45 ` Marek Behún
2026-09-29 15:30 ` Uwe Kleine-König
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=20260928112342.2B4471F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pepe.schlehofer@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.