linux-kernel - Re: Trivial clocksource driver

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]

Date:	Tue, 29 Sep 2015 21:18:10 +0100
From:	Måns Rullgård <mans@...sr.com>
To:	Mason <slash.tmp@...e.fr>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: Re: Trivial clocksource driver

Mason <slash.tmp@...e.fr> writes:

> On 29/09/2015 20:32, Thomas Gleixner wrote:
>
>> On Tue, 29 Sep 2015, Mason wrote:
>> 
>>> I am trying to submit a new ARM port, and Arnd pointed out that the
>>> clocksource code could not live in arch/arm/$PLATFORM, but had to
>>> move to drivers/clocksource (and it had to support DT).
>>>
>>> Did I understand correctly? Is this the right place to submit code
>>> as provided below?
>> 
>> Yes, drivers/clocksource is the right place. You just need to submit a
>> formal patch, which includes a proper subject line, changelog, plus
>> the necessary Makefile and Kconfig modifications.
>
> OK, I'll send a formal patch tomorrow.
> There are no Kconfig modifications, is that OK?

Why don't you use my driver?  It's even simpler, and it works just fine
on the 87xx chip.

https://github.com/mansr/linux-tangox/blob/master/drivers/clocksource/clksrc-tangox.c

-- 
Måns Rullgård
mans@...sr.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/