linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/8] clocksource: owl: Prepare S700
Date: Thu, 7 Dec 2017 14:11:01 +0100	[thread overview]
Message-ID: <f1480e8b-81b8-e425-794a-abbe77387877@linaro.org> (raw)
In-Reply-To: <95e19098-e7a0-424e-3970-5c391605c059@suse.de>

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@suse.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?

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

  -- Daniel


-- 
 <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2017-12-07 13:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 23:34 [PATCH v2 0/8] arm64: Add initial Actions Semi S700 and CubieBoard7 support Andreas Färber
2017-11-13 23:34 ` [PATCH v2 1/8] dt-bindings: arm: actions: Add S700 and CubieBoard7 Andreas Färber
2017-11-16 14:03   ` Andreas Färber
2017-11-13 23:34 ` [PATCH v2 2/8] dt-bindings: timer: Add Actions Semi S700 Andreas Färber
2017-12-07 13:15   ` Daniel Lezcano
2017-11-13 23:34 ` [PATCH v2 3/8] clocksource: owl: Adopt TIMER_OF_DECLARE() Andreas Färber
2017-12-07 13:15   ` Daniel Lezcano
2017-11-13 23:34 ` [PATCH v2 4/8] clocksource: owl: Prepare S700 Andreas Färber
2017-12-04 23:00   ` Andreas Färber
2017-12-07  9:23     ` Daniel Lezcano
2017-12-07 12:47       ` Andreas Färber
2017-12-07 13:11         ` Daniel Lezcano [this message]
2017-12-07 13:16           ` Andreas Färber
2017-12-07 13:16   ` Daniel Lezcano
2017-11-13 23:34 ` [PATCH v2 5/8] arm64: dts: actions: Add S700 and CubieBoard7 Andreas Färber
2017-12-22 10:10   ` Andreas Färber
2017-11-13 23:34 ` [PATCH v2 6/8] dt-bindings: power: Add Actions Semi S700 SPS Andreas Färber
2017-11-16  4:35   ` Rob Herring
2017-11-16 13:42     ` Andreas Färber
2017-11-13 23:34 ` [PATCH v2 7/8] soc: actions: sps: Add S700 Andreas Färber
2017-11-16 14:05   ` Andreas Färber
2017-11-13 23:34 ` [PATCH v2 8/8] arm64: dts: actions: Add S700 SPS node Andreas Färber
2017-11-16 14:16   ` Andreas Färber
2017-12-07  9:20 ` [PATCH v2 0/8] arm64: Add initial Actions Semi S700 and CubieBoard7 support Daniel Lezcano
2017-12-07 11:30   ` Andreas Färber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1480e8b-81b8-e425-794a-abbe77387877@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).