[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191217083254.GD2672708@kroah.com>
Date: Tue, 17 Dec 2019 09:32:54 +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>, linux-kernel@...r.kernel.org,
linux-leds@...r.kernel.org, linux-serial@...r.kernel.org,
kernel@...gutronix.de
Subject: Re: [PATCH v2 0/3] tty/leds: implement a trigger for ttys
On Tue, Dec 17, 2019 at 09:17:15AM +0100, Uwe Kleine-König wrote:
> Hello,
>
> back in November last year I sent my last approach to implement an led
> trigger for UARTs (Message-Id:
> 20181106213739.29628-1-u.kleine-koenig@...gutronix.de). This was parked
> on my todo list since then somewhere far from the top.
>
> This is a new approach. Similar to the netdev trigger the tty trigger
> introduced here periodically checks the statistics related to a given
> tty and if that changed the LED is flashed once.
>
> I had to introduce two functions in the tty layer to be able to get my
> hands on the needed data in the first two patches, the third patch then
> adds the trigger.
I like the idea, seems sane. Minor code nits on the implementation
though...
thanks,
greg k-h
Powered by blists - more mailing lists