From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
Jiri Slaby <jslaby@suse.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v4 0/3] tty/leds: implement a trigger for ttys
Date: Tue, 17 Dec 2019 18:22:32 +0100 [thread overview]
Message-ID: <20191217172232.GC3829986@kroah.com> (raw)
In-Reply-To: <20191217165816.19324-1-u.kleine-koenig@pengutronix.de>
On Tue, Dec 17, 2019 at 05:58:13PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> v3 of this series was sent earlier today starting with Message-Id:
> 20191217150736.1479-1-u.kleine-koenig@pengutronix.de.
>
> v4 only changes patch 3 dropping a few printks, fixing the show callback
> for the dev attribute to match its store function. And I moved
> ledtrig_tty_restart() into the already existing if (tty) {...} block in
> dev_store and dropped the same check from the former function.
>
All looks good to me, so if the LED developers give their ack, I can
take it in my tty tree.
thanks,
greg k-h
next prev parent reply other threads:[~2019-12-17 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 16:58 [PATCH v4 0/3] tty/leds: implement a trigger for ttys Uwe Kleine-König
2019-12-17 16:58 ` [PATCH v4 1/3] tty: rename tty_kopen() and add new function tty_kopen_shared() Uwe Kleine-König
2019-12-17 18:08 ` Jacek Anaszewski
2019-12-17 18:20 ` Greg Kroah-Hartman
2019-12-17 18:27 ` Uwe Kleine-König
2019-12-17 20:19 ` Jacek Anaszewski
2019-12-17 20:23 ` Greg Kroah-Hartman
2019-12-17 16:58 ` [PATCH v4 2/3] tty: new helper function tty_get_icount() Uwe Kleine-König
2019-12-17 16:58 ` [PATCH v4 3/3] leds: trigger: implement a tty trigger Uwe Kleine-König
2019-12-17 17:22 ` Greg Kroah-Hartman [this message]
2019-12-21 18:36 ` [PATCH v4 0/3] tty/leds: implement a trigger for ttys Pavel Machek
2019-12-23 9:58 ` Uwe Kleine-König
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=20191217172232.GC3829986@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmurphy@ti.com \
--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 \
--cc=u.kleine-koenig@pengutronix.de \
/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).