linux-kernel - Re: [GIT pull] timers/core for v5.8

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 for Android: free password hash cracker in your pocket

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

Message-ID: <87mu5kf4cu.fsf@nanos.tec.linutronix.de>
Date:   Wed, 03 Jun 2020 19:26:09 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [GIT pull] timers/core for v5.8

Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Tue, Jun 2, 2020 at 5:09 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>>
>> The truly boring timer and clocksource updates for 5.8:
>>
>>  - Not a single new clocksource or clockevent driver!
>
> The diffstat proved that to be a filthy lie:
>
>>  drivers/clocksource/timer-ti-dm-systimer.c         | 727 +++++++++++++++++++++
>
> comes from
>
>> Tony Lindgren (6):
>>       clocksource/drivers/timer-ti-dm: Add clockevent and clocksource support
>
> Ok, ok, it's "based on existing arch/arm/mach-omap2/timer.c". So I
> guess you considered it one of the device tree cleanups.

Hrm.

> But I'm not fooled by your transparent little white lies.  We will
> never ever have a release without new clocksource drivers.
>
> Sob.

Darn, you just killed my illusion that the new clock* driver frenzy
finally subsides.

Thanks,

        tglx