From: Akinobu Mita <akinobu.mita@gmail.com>
To: linux-block@vger.kernel.org, linux-leds@vger.kernel.org,
linux-nvme@lists.infradead.org
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 0/2] introduce LED block device activity trigger
Date: Sun, 7 Jul 2019 02:58:57 +0900 [thread overview]
Message-ID: <1562435939-15466-1-git-send-email-akinobu.mita@gmail.com> (raw)
This work is inspired by the recent report on linux-nvme mailing list.
disk-activity trigger not working for nvme disk:
http://lists.infradead.org/pipermail/linux-nvme/2019-July/025253.html
This LED block device activity trigger works with any block devices.
Akinobu Mita (2):
leds: move declaration of led_stop_software_blink() to linux/leds.h
block: introduce LED block device activity trigger
block/Makefile | 1 +
block/blk-ledtrig.c | 219 ++++++++++++++++++++++++++++++++++++++++++++++++++
block/blk.h | 13 +++
block/genhd.c | 2 +
drivers/leds/leds.h | 1 -
include/linux/genhd.h | 4 +
include/linux/leds.h | 2 +
7 files changed, 241 insertions(+), 1 deletion(-)
create mode 100644 block/blk-ledtrig.c
Cc: Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>
Cc: Dan Murphy <dmurphy@ti.com>
Cc: Jens Axboe <axboe@kernel.dk>
--
2.7.4
next reply other threads:[~2019-07-06 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 17:58 Akinobu Mita [this message]
2019-07-06 17:58 ` [PATCH 1/2] leds: move declaration of led_stop_software_blink() to linux/leds.h Akinobu Mita
2019-07-06 17:58 ` [PATCH 2/2] block: introduce LED block device activity trigger Akinobu Mita
2019-07-16 20:57 ` Jacek Anaszewski
2019-07-17 14:27 ` Akinobu Mita
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=1562435939-15466-1-git-send-email-akinobu.mita@gmail.com \
--to=akinobu.mita@gmail.com \
--cc=axboe@kernel.dk \
--cc=dmurphy@ti.com \
--cc=fsteiner-mail1@bio.ifi.lmu.de \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=pavel@ucw.cz \
/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).