[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191217172232.GC3829986@kroah.com>
Date: Tue, 17 Dec 2019 18:22:32 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>, Dan Murphy <dmurphy@...com>,
Jiri Slaby <jslaby@...e.com>, kernel@...gutronix.de,
linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
linux-serial@...r.kernel.org
Subject: Re: [PATCH v4 0/3] tty/leds: implement a trigger for ttys
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@...gutronix.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
Powered by blists - more mailing lists