From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: rjw@sisk.pl, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org, patches@linaro.org, lenb@kernel.org,
linus.walleij@linaro.org, rnayak@ti.com, kernel@pengutronix.de,
tglx@linutronix.de
Subject: Re: [PATCH 1/4][resend] cpuidle : handle clockevent notify from the cpuidle framework
Date: Thu, 21 Mar 2013 14:54:15 +0100 [thread overview]
Message-ID: <514B1107.4070403@linaro.org> (raw)
In-Reply-To: <514B0417.6020401@ti.com>
On 03/21/2013 01:59 PM, Santosh Shilimkar wrote:
[ ... ]
> Seems like good clean-up from drivers.
> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
... btw, thanks for reviewing the patches :)
-- 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:[~2013-03-21 13:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 12:21 [PATCH 1/4][resend] cpuidle : handle clockevent notify from the cpuidle framework Daniel Lezcano
2013-03-21 12:21 ` [PATCH 2/4] cpuidle / omap4 : use CPUIDLE_FLAG_TIMER_STOP flag Daniel Lezcano
2013-03-21 13:01 ` Santosh Shilimkar
2013-03-21 13:05 ` Santosh Shilimkar
2013-03-21 13:14 ` Daniel Lezcano
2013-03-21 13:21 ` Santosh Shilimkar
2013-03-22 17:05 ` Kevin Hilman
2013-03-21 12:21 ` [PATCH 3/4] cpuidle / imx6 " Daniel Lezcano
2013-03-21 13:03 ` Santosh Shilimkar
2013-03-21 12:21 ` [PATCH 4/4] cpuidle / ux500 " Daniel Lezcano
2013-03-21 12:59 ` [PATCH 1/4][resend] cpuidle : handle clockevent notify from the cpuidle framework Santosh Shilimkar
2013-03-21 13:52 ` Daniel Lezcano
2013-03-21 14:04 ` Santosh Shilimkar
2013-03-21 14:41 ` Daniel Lezcano
2013-03-21 14:52 ` Santosh Shilimkar
2013-03-21 15:25 ` Lorenzo Pieralisi
2013-03-26 8:41 ` Santosh Shilimkar
2013-03-21 13:54 ` Daniel Lezcano [this message]
2013-03-22 0:41 ` Rafael J. Wysocki
2013-03-22 17:04 ` Kevin Hilman
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=514B1107.4070403@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=kernel@pengutronix.de \
--cc=lenb@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rjw@sisk.pl \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.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 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.