[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4da6f90-d105-f6a4-5c33-1e1fb200738a@suse.de>
Date: Thu, 7 Dec 2017 14:16:21 +0100
From: Andreas Färber <afaerber@...e.de>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: linux-arm-kernel@...ts.infradead.org, support@...ietech.com,
张天益 <tyzhang@...ions-semi.com>,
梅利 <harrymei@...ions-semi.com>,
linux-kernel@...r.kernel.org,
Thomas Liau <thomas.liau@...ions-semi.com>,
张东风 <zhangdf@...ions-semi.com>,
刘炜 <liuwei@...ions-semi.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jeff Chen <jeff.chen@...ions-semi.com>
Subject: Re: [PATCH v2 4/8] clocksource: owl: Prepare S700
Am 07.12.2017 um 14:11 schrieb Daniel Lezcano:
> On 07/12/2017 13:47, Andreas Färber wrote:
>> Am 07.12.2017 um 10:23 schrieb Daniel Lezcano:
>>> On 05/12/2017 00:00, Andreas Färber wrote:
>>>> Hi Daniel,
>>>>
>>>> Am 14.11.2017 um 00:34 schrieb Andreas Färber:
>>>>> Actions S700 has two 2Hz timers like S500, and four TIMx timers like S900.
>>>>>
>>>>> Signed-off-by: Andreas Färber <afaerber@...e.de>
>>>>> ---
>>>>> v1 -> v2:
>>>>> * Adopted TIMER_OF_DECLARE() (Daniel)
>>>>>
>>>>> drivers/clocksource/owl-timer.c | 1 +
>>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> Are you planning to queue this v2 patch for 4.16?
>>>
>>> Yeah, what about the patch 1/8 ?
>>
>> In linux-next already.
>
> Yeah, but that does not mean the patch is merged. Do you mean it is
> merged in arm-soc, so it is visible in linux-next?
No, I am waiting to send my initial 4.16 pull to arm-soc and wanted to
clarify what (if anything) from this series can still go into that pull.
>> If you take 2-4, I can take 5; if you'd rather have me take the binding,
>> fine with me as well.
>
> I will take patches 2-4.
Thanks,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists