From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [PATCH v3 0/3] tty/leds: implement a trigger for ttys
Date: Tue, 17 Dec 2019 16:07:33 +0100 [thread overview]
Message-ID: <20191217150736.1479-1-u.kleine-koenig@pengutronix.de> (raw)
Hello,
next iteration of the tty-led-trigger series. This addresses the review
comments I got from Greg.
This depends on patch "tty: drop useless variable initialisation in
tty_kopen()" which is already on tty-testing.
Best regards
Uwe
Uwe Kleine-König (3):
tty: rename tty_kopen() and add new function tty_kopen_shared()
tty: new helper function tty_get_icount()
leds: trigger: implement a tty trigger
drivers/leds/trigger/Kconfig | 7 ++
drivers/leds/trigger/Makefile | 1 +
drivers/leds/trigger/ledtrig-tty.c | 159 ++++++++++++++++++++++++++++
drivers/staging/speakup/spk_ttyio.c | 2 +-
drivers/tty/tty_io.c | 87 +++++++++++----
include/linux/tty.h | 7 +-
6 files changed, 238 insertions(+), 25 deletions(-)
create mode 100644 drivers/leds/trigger/ledtrig-tty.c
--
2.24.0
next reply other threads:[~2019-12-17 15:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 15:07 Uwe Kleine-König [this message]
2019-12-17 15:07 ` [PATCH v3 1/3] tty: rename tty_kopen() and add new function tty_kopen_shared() Uwe Kleine-König
2019-12-17 15:07 ` [PATCH v3 2/3] tty: new helper function tty_get_icount() Uwe Kleine-König
2019-12-17 15:07 ` [PATCH v3 3/3] leds: trigger: implement a tty trigger Uwe Kleine-König
2019-12-17 15:27 ` Greg Kroah-Hartman
2019-12-17 16:23 ` Uwe Kleine-König
2019-12-17 17:21 ` Greg Kroah-Hartman
2019-12-17 20:27 ` Jacek Anaszewski
2019-12-17 21:08 ` Uwe Kleine-König
2019-12-18 21:33 ` Jacek Anaszewski
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=20191217150736.1479-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=dmurphy@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jslaby@suse.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-serial@vger.kernel.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).