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,
	bo.zhang@nxp.com, jonas.gorski@gmail.com
Subject: [GIT PULL] LED fixes 4.12-rc6
Date: Sat, 17 Jun 2017 13:36:22 +0200	[thread overview]
Message-ID: <1497699382-3160-1-git-send-email-jacek.anaszewski@gmail.com> (raw)

Hi Linus,

Please pull two LED fixes:
- fix signal source assignment for leds-bcm6328
- revert patch that intended to fix LED behavior on suspend but it
  had a side effect preventing suspend at all due to uevent being
  sent on trigger removal; the original problem will need to get more
  investigation

The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:

  Linux 4.12-rc1 (2017-05-13 13:19:49 -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_4.12-rc6

for you to fetch changes up to 436c4c45b5b9562b59cedbb51b7343ab4a6dd8cc:

  Revert "leds: handle suspend/resume in heartbeat trigger" (2017-06-13 20:37:01 +0200)

Best regards,
Jacek Anaszewski

----------------------------------------------------------------
LED fixes for 4.12-rc6

----------------------------------------------------------------
Jonas Gorski (1):
      leds: bcm6328: fix signal source assignment for leds 4 to 7

Zhang Bo (1):
      Revert "leds: handle suspend/resume in heartbeat trigger"

 drivers/leds/leds-bcm6328.c              |  4 ++--
 drivers/leds/trigger/ledtrig-heartbeat.c | 31 -------------------------------
 2 files changed, 2 insertions(+), 33 deletions(-)

                 reply	other threads:[~2017-06-17 11:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1497699382-3160-1-git-send-email-jacek.anaszewski@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=bo.zhang@nxp.com \
    --cc=jonas.gorski@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).