From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] timers/core for v5.8
Date: Wed, 03 Jun 2020 19:26:09 +0200 [thread overview]
Message-ID: <87mu5kf4cu.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAHk-=wiQr=wMrjpDXfvR=g+muNr4ST6=4O_jv6pOuTbtdbE_aw@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Tue, Jun 2, 2020 at 5:09 AM Thomas Gleixner <tglx@linutronix.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
next prev parent reply other threads:[~2020-06-03 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 12:08 [GIT pull] irq/core for v5.8 Thomas Gleixner
2020-06-02 12:08 ` [GIT pull] timers/core " Thomas Gleixner
2020-06-03 17:16 ` Linus Torvalds
2020-06-03 17:26 ` Thomas Gleixner [this message]
2020-06-03 18:15 ` pr-tracker-bot
2020-06-03 18:15 ` [GIT pull] irq/core " pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu5kf4cu.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).