public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: grygorii.strashko@ti•com (Grygorii Strashko)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH] ARM: clocksource: make ARM_GLOBAL_TIMER selectable
Date: Mon, 4 Apr 2016 18:12:30 +0300	[thread overview]
Message-ID: <5702845E.90606@ti.com> (raw)
In-Reply-To: <56EAB44D.7020902@linaro.org>

Hi Daniel,
On 03/17/2016 03:42 PM, Daniel Lezcano wrote:
> On 03/08/2016 11:55 AM, Grygorii Strashko wrote:
>> Yeah. Thanks
>>
>> I'll re-send it after 4.6-rc.
>> But What I'm not fully understand is how to get it merged taking into 
>> account that
>> it touches few maches & clocksource :(
> 
> This is not a problem. Send it based on timers/core from the tip tree 
> and Cc the maintainers for the maches dir. As soon as they ack the 
> patches, I will merge it through my tree.
> 

I've rebased my patch on top of 4.6-rc2 and extended it on new mach
arch/arm/mach-artpec.

Then, as you've suggested, I've tried to apply it on top of 
kernel-tip/timers/core
kernel-tip := git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

but seems timers/core is obsolete (It doesn't contain arch/arm/mach-artpec yet).

Should I wait more or can resend it basing on top of  4.6-rc2?



-- 
regards,
-grygorii

  reply	other threads:[~2016-04-04 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 18:20 [RFC PATCH] ARM: clocksource: make ARM_GLOBAL_TIMER selectable Grygorii Strashko
2016-02-04 22:41 ` Sören Brinkmann
2016-02-04 23:14   ` Moritz Fischer
2016-02-04 23:39     ` Sören Brinkmann
2016-02-26 13:03       ` Grygorii Strashko
2016-02-26 15:27         ` Sören Brinkmann
2016-03-08 10:55           ` Grygorii Strashko
2016-03-17 13:42             ` Daniel Lezcano
2016-04-04 15:12               ` Grygorii Strashko [this message]
2016-04-05  0:03                 ` Daniel Lezcano

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=5702845E.90606@ti.com \
    --to=grygorii.strashko@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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