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: <560AFED6.3020400@free.fr>
Date:	Tue, 29 Sep 2015 23:12:54 +0200
From:	Mason <slash.tmp@...e.fr>
To:	Mans Rullgard <mans@...sr.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Daniel Lezcano <daniel.lezcano@...aro.org>
Subject: Re: Trivial clocksource driver

Hello Mans,

On 29/09/2015 22:18, Måns Rullgård wrote:

> Mason 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

As you know, I am using two of your complex drivers, namely
ethernet and interrupt controller (which would have taken me
several weeks to write). I will be submitting them upstream
shortly, is that OK with you?

I'm not using this particular driver of yours because I had
already written the code, and porting it to DT was a good
learning process. This is probably my only opportunity to
actually write any kind of code for this port.

Regards.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ