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, 5 Dec 2017 11:16:20 +0100
From:   Alexandre Torgue <alexandre.torgue@...com>
To:     Daniel Lezcano <daniel.lezcano@...aro.org>,
        Benjamin Gaignard <benjamin.gaignard@...aro.org>,
        <robh+dt@...nel.org>, <mark.rutland@....com>,
        <linux@...linux.org.uk>, <mcoquelin.stm32@...il.com>,
        <tglx@...utronix.de>, <ludovic.barre@...com>,
        <julien.thierry@....com>, <sudeep.holla@....com>, <arnd@...db.de>
CC:     <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v8 0/6] stm32 clocksource driver rework



On 12/05/2017 11:15 AM, Daniel Lezcano wrote:
> On 05/12/2017 11:12, Alexandre Torgue wrote:
> [ ... ]
> 
>>> Benjamin Gaignard (6):
>>>     clocksource: timer_of: rename timer_of_exit to timer_of_cleanup
>>>     clocksource: stm32: convert driver to timer_of
>>>     clocksource: stm32: increase min delta value
>>>     clocksource: stm32: only use 32 bits timers
>>>     clocksource: stm32: add clocksource support
>>>     arm: dts: stm32: remove useless clocksource nodes
>>>
>>>    arch/arm/boot/dts/stm32f429.dtsi  |  32 -----
>>>    arch/arm/boot/dts/stm32f746.dtsi  |  32 -----
>>>    drivers/clocksource/Kconfig       |   1 +
>>>    drivers/clocksource/timer-of.c    |   9 +-
>>>    drivers/clocksource/timer-of.h    |   2 +-
>>>    drivers/clocksource/timer-stm32.c | 242
>>> ++++++++++++++++++++------------------
>>>    6 files changed, 138 insertions(+), 180 deletions(-)
>>>
>>
>> What is the status of this patch-set ? Is there a chance to have it for
>> v4.16 ?
> 
> I will take care of reviewing them this week. It is in my todo list.
> 
> 
Thanks Daniel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ