From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Joel Stanley <joel@jms.id.au>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Ryan Chen <ryan_chen@aspeedtech.com>
Subject: Re: [PATCH] clocksource: moxart: Add AST2500 compatible string
Date: Tue, 30 May 2017 10:54:40 +0200 [thread overview]
Message-ID: <1a165856-6863-ad51-d66c-eda062f4d98e@linaro.org> (raw)
In-Reply-To: <CACRpkdYbicYPJvaeTMpHSn4F77ognBfnEbj7OknFiZgfK1qizA@mail.gmail.com>
On 30/05/2017 09:44, Linus Walleij wrote:
> On Sun, May 28, 2017 at 8:27 PM, Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
>> On 28/05/2017 15:59, Linus Walleij wrote:
>>> On Tue, May 16, 2017 at 9:58 AM, Andrew Jeffery <andrew@aj.id.au> wrote:
>>>
>>>> Also clean up space-before-tab issues in the documentation.
>>>>
>>>> Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
>>>
>>> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>>>
>>> Does this collide with Daniel's 2500 patch?
>>>
>>> Sorry for the mess, tell me if I need to fix something up :(
>>
>> It is ok, an usual collision change to be fixed when merging ;)
>>
>> By the way, can you have a look at fttmr010_read_sched_clock to remove
>> the local_fttmr->count_down test?
>
> I guess what we can do is make two different sched_clock()
> callbacks: one for upward and one for downward counting.
>
> Would you like an optimization like that?
>
> (It makes sense.)
Yes, thanks Linus!
-- 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
next prev parent reply other threads:[~2017-05-30 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 7:58 [PATCH] clocksource: moxart: Add AST2500 compatible string Andrew Jeffery
[not found] ` <20170516075840.23130-1-andrew-zrmu5oMJ5Fs@public.gmane.org>
2017-05-16 10:03 ` Joel Stanley
2017-05-23 0:07 ` Rob Herring
2017-05-25 20:28 ` Daniel Lezcano
2017-05-26 1:12 ` Andrew Jeffery
2017-05-28 14:00 ` Linus Walleij
2017-05-28 13:59 ` Linus Walleij
[not found] ` <CACRpkdZsbzwBKRj1FXAoCW9nD357SNNK8t=gOO-OBtV_pwjpKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-28 18:27 ` Daniel Lezcano
[not found] ` <0f526d58-3138-d7ea-0dc7-5ef623fb0547-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-05-30 7:44 ` Linus Walleij
2017-05-30 8:54 ` Daniel Lezcano [this message]
[not found] ` <1a165856-6863-ad51-d66c-eda062f4d98e-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-05-30 9:53 ` Linus Walleij
[not found] ` <CACRpkdYtq09MYz4xcgYOpKDe406YzatnRKNmVyP9QRU2z5x2_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-30 10: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=1a165856-6863-ad51-d66c-eda062f4d98e@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ryan_chen@aspeedtech.com \
--cc=tglx@linutronix.de \
/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).