From: holgerschurig@gmail.com (Holger Schurig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] leds: trigger: Introduce a kernel panic LED trigger
Date: Thu, 31 Mar 2016 14:56:01 +0200 [thread overview]
Message-ID: <878u0yst5q.fsf@gmail.com> (raw)
In-Reply-To: <20160330191109.GA27372@laptop.cereza> (Ezequiel Garcia's message of "Wed, 30 Mar 2016 16:11:09 -0300")
> (Interestingly, it also blinks the LEDs on a USB keyboard!)
Assuming USB is still working after a kernel panic ...
next prev parent reply other threads:[~2016-03-31 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 20:35 [PATCH 0/3] Add a new LED trigger for kernel panics (and use it) Ezequiel Garcia
2016-03-29 20:35 ` [PATCH 1/3] leds: trigger: Introduce a kernel panic LED trigger Ezequiel Garcia
2016-03-30 9:29 ` Jacek Anaszewski
2016-03-30 19:11 ` Ezequiel Garcia
2016-03-31 7:04 ` Jacek Anaszewski
2016-03-31 7:28 ` Jacek Anaszewski
2016-03-31 12:56 ` Holger Schurig [this message]
2016-03-29 20:35 ` [PATCH 2/3] ARM: configs: Enable panic LED trigger on s3c2410 Ezequiel Garcia
2016-03-29 20:35 ` [PATCH 3/3] ARM: s3c24xx: Use the panic LED trigger for GTA02 Ezequiel Garcia
2016-03-29 20:44 ` [PATCH 0/3] Add a new LED trigger for kernel panics (and use it) Arnd Bergmann
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=878u0yst5q.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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