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 5.5-rc8
Date: Wed, 22 Jan 2020 21:17:11 +0100 [thread overview]
Message-ID: <20200122201711.GA29496@amd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1945 bytes --]
The following changes since commit d1eef1c619749b2a57e514a3fa67d9a516ffa919:
Linux 5.5-rc2 (2019-12-15 15:16:08 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git/ tags/leds-5.5-rc8
for you to fetch changes up to 43108c72cf1d518f3ce62d3b1c8a9ffa38ddc28b:
leds: lm3532: add pointer to documentation and fix typo (2020-01-22 21:08:24 +0100)
----------------------------------------------------------------
Changes for Linus for -rc8.
Jacek's commit is why I'm requesting this pull; it fixes regression in
debugging output in sysfs. Others are just bugfixes that should be
safe. Everything was in -next for while.
Now, I noticed one commit is from "Pavel" and it is supposed to be
from "Pavel Machek". Can you pull it anyway, or should I redo the
request? Or feel free to edit/drop that commit.
Best regards,
Pavel
----------------------------------------------------------------
Bartosz Golaszewski (1):
led: max77650: add of_match table
Jacek Anaszewski (1):
leds: gpio: Fix uninitialized gpio label for fwnode based probe
Pavel (1):
leds: lm3532: add pointer to documentation and fix typo
Pavel Machek (2):
ledtrig-pattern: fix email address quoting in MODULE_AUTHOR()
leds: rb532: cleanup whitespace
Sakari Ailus (1):
leds-as3645a: Drop fwnode reference on ignored node
drivers/leds/leds-as3645a.c | 3 ++-
drivers/leds/leds-gpio.c | 10 +++++++++-
drivers/leds/leds-lm3532.c | 3 ++-
drivers/leds/leds-max77650.c | 7 +++++++
drivers/leds/leds-rb532.c | 1 -
drivers/leds/trigger/ledtrig-pattern.c | 4 ++--
6 files changed, 22 insertions(+), 6 deletions(-)
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2020-01-22 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 20:17 Pavel Machek [this message]
2020-01-22 21:01 ` [GIT PULL] LEDs changes for 5.5-rc8 Linus Torvalds
2020-01-22 21:05 ` 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=20200122201711.GA29496@amd \
--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;
as well as URLs for NNTP newsgroup(s).