From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>,
kernel list <linux-kernel@vger.kernel.org>,
jacek.anaszewski@gmail.com, linux-leds@vger.kernel.org
Subject: [GIT PULL] LEDs changes for v5.16-rc1
Date: Mon, 1 Nov 2021 12:13:54 +0100 [thread overview]
Message-ID: <20211101111354.GA29161@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/ tags/leds-5.16-rc1
for you to fetch changes up to 97b31c1f8eb865bc3aa5f4a08286a6406d782ea8:
leds: trigger: Disable CPU trigger on PREEMPT_RT (2021-10-13 20:07:57 +0200)
----------------------------------------------------------------
Johannes pointed out that locking is still problematic with triggers
list, attempt to solve that by using RCU.
----------------------------------------------------------------
Arnd Bergmann (1):
led-class-flash: fix -Wrestrict warning
Johannes Berg (1):
leds: trigger: use RCU to protect the led_cdevs list
Sebastian Andrzej Siewior (1):
leds: trigger: Disable CPU trigger on PREEMPT_RT
drivers/leds/led-class-flash.c | 2 +-
drivers/leds/led-triggers.c | 41 +++++++++++++++++++++--------------------
drivers/leds/trigger/Kconfig | 1 +
include/linux/leds.h | 2 +-
4 files changed, 24 insertions(+), 22 deletions(-)
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2021-11-01 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 11:13 Pavel Machek [this message]
2021-11-02 2:20 ` pr-tracker-bot
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=20211101111354.GA29161@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®