From: Lee Jones <lee@kernel.org>
To: Craig McQueen <craig@mcqueen.au>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH v2 0/1] Introduce userspace LED triggers driver
Date: Fri, 14 Mar 2025 10:57:51 +0000 [thread overview]
Message-ID: <20250314105751.GE3890718@google.com> (raw)
In-Reply-To: <20250311013143.371930-1-craig@mcqueen.au>
On Tue, 11 Mar 2025, Craig McQueen wrote:
> I've done some significant rework since my original submission of this.
>
> * Moved and renamed driver to drivers/leds/trigger/ledtrig-user.c,
> following kernel arrangement of trigger drivers.
> But note the char device name and uapi header file are still named
> 'uledtriggers'.
> * Fixed a mutex reentrancy issue with the 'activate' function.
> * Code refactoring and add comments.
> * Add new documentation page to index.
>
> Craig McQueen (1):
> leds: Introduce userspace LED triggers driver
>
> Documentation/leds/index.rst | 1 +
> Documentation/leds/ledtrig-user.rst | 36 +++
> drivers/leds/trigger/Kconfig | 10 +
> drivers/leds/trigger/Makefile | 1 +
> drivers/leds/trigger/ledtrig-user.c | 348 ++++++++++++++++++++++++++++
> include/uapi/linux/uledtriggers.h | 123 ++++++++++
> 6 files changed, 519 insertions(+)
> create mode 100644 Documentation/leds/ledtrig-user.rst
> create mode 100644 drivers/leds/trigger/ledtrig-user.c
> create mode 100644 include/uapi/linux/uledtriggers.h
This is a fairly large inclusion.
I'm going to let this sit on the LEDs list for a few more weeks.
You should also consider always Cc:ing LKML, since a lot of useful
reviewers don't subscribe to all of the little subsystem lists.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2025-03-14 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 1:28 [PATCH v2 0/1] Introduce userspace LED triggers driver Craig McQueen
2025-03-11 1:28 ` [PATCH v2 1/1] leds: " Craig McQueen
2025-03-25 13:15 ` Pavel Machek
2025-03-27 2:13 ` Craig McQueen
2025-04-11 10:08 ` Pavel Machek
2025-03-11 1:57 ` [PATCH v2 0/1] " Craig McQueen
2025-03-14 10:57 ` 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=20250314105751.GE3890718@google.com \
--to=lee@kernel.org \
--cc=craig@mcqueen.au \
--cc=linux-leds@vger.kernel.org \
/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