linux-kernel - Re: [PATCH v11] leds: trigger: implement a tty trigger

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YC7aQ7LKjr+ZRo8w@kroah.com>
Date:   Thu, 18 Feb 2021 22:21:07 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>
Cc:     Pavel Machek <pavel@....cz>, kernel@...gutronix.de,
        Johan Hovold <johan@...nel.org>, linux-kernel@...r.kernel.org,
        Jacek Anaszewski <jacek.anaszewski@...il.com>,
        linux-serial@...r.kernel.org, Jiri Slaby <jslaby@...e.com>,
        linux-leds@...r.kernel.org, Dan Murphy <dmurphy@...com>
Subject: Re: [PATCH v11] leds: trigger: implement a tty trigger

On Thu, Feb 18, 2021 at 10:19:48PM +0100, Uwe Kleine-König wrote:
> Hello Pavel,
> 
> On Thu, Feb 18, 2021 at 02:33:52PM +0100, Pavel Machek wrote:
> > > > > so that I can queue it up?
> > > > 
> > > > Oh, so you are LED maintainer now? My congratulations.
> > > > (Honestly, do you plan to apply this without their ack? Not that I'm
> > > > against you doing that, I'm happy if I can archive this patch series as
> > > > done, but I'm a bit surprised.)
> > > 
> > > It's drug on for so long now, the infrastructure that this driver needs
> > > has now bee merged, so I see no reason why this driver can't be taken
> > > now.  I offered up a "any objections?" in the past, and have gotten
> > > none, so I will take that for quiet acceptance :)
> > 
> > Thanks for taking the infrastructure patches, but please drop this
> > one.
> 
> Given it is already part of Greg's pull request I wonder if we need an
> incremental patch instead?

An incremental patch is easier, thanks, I can't "drop" a patch already
in my public tree.

greg k-h