linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Subject: [GIT PULL] LED fixes for 5.4-rc3.
Date: Tue,  8 Oct 2019 22:42:58 +0200	[thread overview]
Message-ID: <20191008204258.22196-1-jacek.anaszewski@gmail.com> (raw)

Hi Linus,

Please pull two patches for 5.4-rc3:

- fix a leftover from earlier stage of development in the documentation
  of recently added led_compose_name() and fix old mistake in
  the documentation of led_set_brightness_sync() parameter name.

- MAINTAINERS: add pointer to Pavel Machek's linux-leds.git tree.
  Pavel is going to take over LED tree maintainership
  from myself.

The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:

  Linux 5.4-rc1 (2019-09-30 10:35:40 -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.4-rc3

for you to fetch changes up to 4050d21d2009faccae5cab74eeb9f460f25d5108:

  Add my linux-leds branch to MAINTAINERS (2019-10-08 22:09:08 +0200)

Thanks,
Jacek Anaszewski

----------------------------------------------------------------
LED fixes for 5.4-rc3.
----------------------------------------------------------------
Dan Murphy (1):
      leds: core: Fix leds.h structure documentation

Pavel Machek (1):
      Add my linux-leds branch to MAINTAINERS

 MAINTAINERS          | 1 +
 include/linux/leds.h | 5 ++---
 2 files changed, 3 insertions(+), 3 deletions(-)

             reply	other threads:[~2019-10-08 20:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 20:42 Jacek Anaszewski [this message]
2019-10-08 23:00 ` [GIT PULL] LED fixes for 5.4-rc3 pr-tracker-bot
2019-10-09  8:36 ` Pavel Machek
2019-10-09 12:55 ` leds in -next -- update address was " Pavel Machek
2019-10-10  0:36   ` Stephen Rothwell

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=20191008204258.22196-1-jacek.anaszewski@gmail.com \
    --to=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).