linux-kernel - Re: [PULL REQUEST] i2c for 4.20

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-=wgAJXs32MZNWNO9HjMmgtV9kWmDvjQS7zcFg0PVgJyHog@mail.gmail.com>
Date:   Sat, 10 Nov 2018 07:06:52 -0600
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     wsa@...-dreams.de
Cc:     linux-i2c@...r.kernel.org,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        peda@...ntia.se, brgl@...ev.pl
Subject: Re: [PULL REQUEST] i2c for 4.20

On Sat, Nov 10, 2018 at 5:20 AM Wolfram Sang <wsa@...-dreams.de> wrote:
>
> I hope the rc1 rule still applies for this new driver. It consists of the I2C
> master part and UCSI client part which has the needed ack from Heikki.

I've pulled it, but please don't do this again.

The "New driver" rule has become pretty much historical, simply
because releases have been regular enough that it doesn't much make
much sense, and we just have't had the kinds of "basic support"
drivers that make sense pushing out as early as possible just to get
people able to use a machine at all. So in practice, the "new driver"
rule has become a "new ID or quirk" rule.

The nVidia i2c support doesn't sound so special that it couldn't have
waited until the merge window.

                    Linus