From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: sun5i: Refactor the current code
Date: Thu, 5 Mar 2015 16:44:20 +0100 [thread overview]
Message-ID: <20150305154420.GX4911@lukather> (raw)
In-Reply-To: <1425565972-30316-1-git-send-email-daniel.lezcano@linaro.org>
On Thu, Mar 05, 2015 at 03:32:52PM +0100, Daniel Lezcano wrote:
> From: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> Refactor the code in order to remove the global variables and split the clock
> source and clock events registration in order to ease the addition of the clock
> notifiers needed to handle the parent clock rate changes.
>
> [dlezcano] : Fixed conflict with commit 1096be084ac59927158ce80ff1d31c33eed0e565
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
It looks good, thanks for taking care of this!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150305/41c6d9f9/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clocksource: sun5i: Refactor the current code
Date: Thu, 5 Mar 2015 16:44:20 +0100 [thread overview]
Message-ID: <20150305154420.GX4911@lukather> (raw)
In-Reply-To: <1425565972-30316-1-git-send-email-daniel.lezcano@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Thu, Mar 05, 2015 at 03:32:52PM +0100, Daniel Lezcano wrote:
> From: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> Refactor the code in order to remove the global variables and split the clock
> source and clock events registration in order to ease the addition of the clock
> notifiers needed to handle the parent clock rate changes.
>
> [dlezcano] : Fixed conflict with commit 1096be084ac59927158ce80ff1d31c33eed0e565
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
It looks good, thanks for taking care of this!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-05 15:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 10:20 [PATCH v3 0/5] clocksource: sun5i: Support parent clock rate changes Maxime Ripard
2015-03-05 10:20 ` Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 1/5] clocksource: sun5i: Switch to request_irq Maxime Ripard
2015-03-05 10:20 ` Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 2/5] clocksource: sun5i: Use of_io_request_and_map Maxime Ripard
2015-03-05 10:20 ` Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 3/5] clocksource: sun5i: Remove sched_clock Maxime Ripard
2015-03-05 10:20 ` Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 4/5] clocksource: sun5i: Refactor the current code Maxime Ripard
2015-03-05 10:20 ` Maxime Ripard
2015-03-05 14:30 ` Daniel Lezcano
2015-03-05 14:30 ` Daniel Lezcano
2015-03-05 14:32 ` [PATCH] " Daniel Lezcano
2015-03-05 14:32 ` Daniel Lezcano
2015-03-05 15:44 ` Maxime Ripard [this message]
2015-03-05 15:44 ` Maxime Ripard
2015-03-05 10:20 ` [PATCH v3 5/5] clocksource: sun5i: Add clock notifiers Maxime Ripard
2015-03-05 10:20 ` Maxime Ripard
2015-03-19 22:53 ` [PATCH v3 0/5] clocksource: sun5i: Support parent clock rate changes Maxime Ripard
2015-03-19 22:53 ` Maxime Ripard
2015-03-20 14:04 ` Daniel Lezcano
2015-03-20 14:04 ` Daniel Lezcano
2015-03-20 20:56 ` Maxime Ripard
2015-03-20 20:56 ` Maxime Ripard
2015-03-21 10:43 ` Hans de Goede
2015-03-21 10:43 ` Hans de Goede
2015-03-23 16:54 ` Maxime Ripard
2015-03-23 16:54 ` Maxime Ripard
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=20150305154420.GX4911@lukather \
--to=maxime.ripard@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.