linux-kernel - Re: [GIT PULL] LEDs chagnes for v5.11-rc

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: <CAHk-=wih0mO6E4cvrAypwPu6xe--DziANaRmqhoRgdX9cM0shw@mail.gmail.com>
Date:   Sun, 31 Jan 2021 11:26:42 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Pavel Machek <pavel@....cz>
Cc:     kernel list <linux-kernel@...r.kernel.org>,
        Jacek Anaszewski <jacek.anaszewski@...il.com>,
        Linux LED Subsystem <linux-leds@...r.kernel.org>
Subject: Re: [GIT PULL] LEDs chagnes for v5.11-rc

On Sun, Jan 31, 2021 at 1:43 AM Pavel Machek <pavel@....cz> wrote:
>
> This pull is due to "leds: trigger: fix potential deadlock with
> libata" -- people find the warn annoying. It also contains new driver
> (still should be okay late in -rcs, right?) and two trivial fixes.

I've pulled it, but please don't add new drivers in -rc's.

Yes, we traditionally accepted them as hardware enablement, but
honestly, our development cycles are so reliable and consistent these
days that it makes very little sense any more.

So aim for just new device ID additions rather than new drivers,
unless it's some *hugely* popular hardware that actually causes
problems for people bootstrapping the system (ie things like a disk or
network driver from a major company that is expected to actually be
widely available and an actual issue for people trying to install
Linux on their own).

                   Linus