From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
jacek.anaszewski@gmail.com, kjlu@umn.edu,
linux@rasmusvillemoes.dk, rafal@milecki.pl
Subject: [GIT PULL] LED fixes for 5.1-rc3
Date: Sat, 30 Mar 2019 19:39:42 +0100 [thread overview]
Message-ID: <20190330183942.6589-1-jacek.anaszewski@gmail.com> (raw)
Hi Linus,
Please pull LED fixes for 5.1-rc3.
ledtrig-netdev fixes:
- fix refcnt leak on interface rename
- use memcpy in device_name_store() to avoid including garbage from
a previous, longer value in the device_name
leds-pca9532:
- fix a potential NULL pointer dereference in case of_match_device()
cannot find a match
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git tags/led-fixes-for-5.1-rc3
for you to fetch changes up to 909346433064b8d840dc82af26161926b8d37558:
leds: trigger: netdev: use memcpy in device_name_store (2019-03-30 19:09:32 +0100)
Thanks,
Jacek Anaszewski
----------------------------------------------------------------
LED fixes for 5.1-rc3
----------------------------------------------------------------
Kangjie Lu (1):
leds: pca9532: fix a potential NULL pointer dereference
Rafał Miłecki (1):
leds: trigger: netdev: fix refcnt leak on interface rename
Rasmus Villemoes (1):
leds: trigger: netdev: use memcpy in device_name_store
drivers/leds/leds-pca9532.c | 8 ++++++--
drivers/leds/trigger/ledtrig-netdev.c | 16 +++++++---------
2 files changed, 13 insertions(+), 11 deletions(-)
next reply other threads:[~2019-03-30 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 18:39 Jacek Anaszewski [this message]
2019-03-30 19:30 ` [GIT PULL] LED fixes for 5.1-rc3 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=20190330183942.6589-1-jacek.anaszewski@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rafal@milecki.pl \
--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).