linux-kernel - Re: [PATCH v2 06/15] clocksource/drivers/timer-milbeaut: Introduce timer for Milbeaut SoCs

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: <feb7c60c-ed9a-1ff0-0871-d9b3fc7a40dc@socionext.com>
Date:   Fri, 15 Feb 2019 11:25:41 +0900
From:   "Sugaya, Taichi" <sugaya.taichi@...ionext.com>
To:     Arnd Bergmann <arnd@...db.de>,
        Daniel Lezcano <daniel.lezcano@...aro.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Arnd Bergmann <arnd.bergmann@...aro.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Takao Orito <orito.takao@...ionext.com>,
        Kazuhiro Kasai <kasai.kazuhiro@...ionext.com>,
        Shinji Kanematsu <kanematsu.shinji@...ionext.com>,
        Jassi Brar <jaswinder.singh@...aro.org>,
        Masami Hiramatsu <masami.hiramatsu@...aro.org>,
        linux-soc@...r.kernel.org
Subject: Re: [PATCH v2 06/15] clocksource/drivers/timer-milbeaut: Introduce
 timer for Milbeaut SoCs

Hi,


On 2019/02/15 0:18, Arnd Bergmann wrote:
> On Thu, Feb 14, 2019 at 3:44 PM Daniel Lezcano
> <daniel.lezcano@...aro.org> wrote:
>>
>> On 13/02/2019 11:34, Sugaya, Taichi wrote:
>>> Hi,
>>>
>>> On 2019/02/12 18:06, Daniel Lezcano wrote:
>>>> On 08/02/2019 13:26, Sugaya Taichi wrote:
>>>>> Add timer driver for Milbeaut SoCs series.
>>>>>
>>>>> The timer has two 32-bit width down counters, one of which is configured
>>>>> as a clockevent device and the other is configured as a clock source.
>>>>>
>>>>> Signed-off-by: Sugaya Taichi <sugaya.taichi@...ionext.com>
>>>>
>>>> Do want me to take it through my tree?
>>>>
>>>
>>> Yes, please.
>>>
>>> By the way, the patch series includes other sub-system drivers, so
>>> should it be splitted into each driver patch ?
>>
>> Well usually changes are per sub-systems but in case of first submission
>> you may ask linux-soc@ team to take all the patches together with the
>> acked-by tags from those subsystems maintainer.
>>
>> Added in Cc: Arnd@ and linux-soc@
>>
>> I'll wait a bit before applying the patch you clarify this.
> 
> Yes, I think merging them all together is best here.
> 
> I saw the patches fly past but did not do a complete review,
> but if all other review comments are addressed, I'd suggest
> sending the entire series for inclusion to linux-soc@...r.kernel.org
> with the Acked-by/Reviewed-by tags from subsystem maintainers
> added in.
> 
>       Arnd
> 

Thank you for suggestion.
OK. I will send the series to the ML with the Acked-by/Reviewed-by tags.

Thanks,
Sugaya Taichi