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: Tue, 8 Mar 2016 17:55:51 +0700 [thread overview]
Message-ID: <56DEAFB7.50105@ti.com> (raw)
In-Reply-To: <20160226152714.GD3173@xsjsorenbubuntu>
On 02/26/2016 10:27 PM, S?ren Brinkmann wrote:
> On Fri, 2016-02-26 at 15:03:19 +0200, Grygorii Strashko wrote:
>> On 02/05/2016 01:39 AM, S?ren Brinkmann wrote:
>>> On Thu, 2016-02-04 at 15:14:47 -0800, Moritz Fischer wrote:
>>>> Hi Soeren,
>>>>
>>>> On Thu, Feb 4, 2016 at 2:41 PM, S?ren Brinkmann
>>>> <soren.brinkmann@xilinx.com> wrote:
>>>>
>>>>> But with this change the 'if !CPU_FREQ' becomes obsolete.
>>>> I'm confused, could you explain that statement? You don't want people
>>>> accidentally running with GT when CPU_FREQ is on, right?
>>>
>>> Correct. But with this Kconfig rework you can just deselect it in
>>> Kconfig. The generic HAVE_GT could always be selected.
>>>
>>
>>
>> Don't know whom should i ask - but what will be the final conclusion here?
>> Can it be merged?
>
> I think we don't break anything either way. Would just be some
> additional clean up to get rid of that mentioned constraint (which
> doesn't really work well anyway in the multi-arch kernel). So, no real
> objections to merging it from my side.
>
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 :(
--
regards,
-grygorii
next prev parent reply other threads:[~2016-03-08 10:55 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 [this message]
2016-03-17 13:42 ` Daniel Lezcano
2016-04-04 15:12 ` Grygorii Strashko
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=56DEAFB7.50105@ti.com \
--to=grygorii.strashko@ti.com \
--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).