From: "Heiko Stübner" <heiko@sntech.de>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, ben-linux@fluff.org,
linaro-dev@lists.linaro.org, patches@linaro.org
Subject: Re: [PATCH 0/2] ARM: S3C64xx: cpuidle cleanups
Date: Mon, 14 May 2012 10:52:46 +0200 [thread overview]
Message-ID: <201205141052.47567.heiko@sntech.de> (raw)
In-Reply-To: <4FB048E4.8070405@linaro.org>
Am Montag, 14. Mai 2012, 01:51:00 schrieb Daniel Lezcano:
> On 05/09/2012 04:08 PM, Daniel Lezcano wrote:
> > These couple of patches use the new cpuidle core api to refactor
> > some part of the code. The first one declares the states directly
> > in the driver declaration and the second one use the timekeeping
> > flag to let the cpuidle core to compute the idle time.
> >
> > I don't have this board, I was not able to test these patches.
> >
> > Daniel Lezcano (2):
> > ARM: s3c64xx: cpuidle - declare the states with the new api
> > ARM: s3c64xx: cpuidle - use timekeeping wrapper
>
> Are these patches ok for inclusion ?
you might want to include the maintainer
Kukjin Kim <kgene.kim@samsung.com>
and the samsung list
linux-samsung-soc@vger.kernel.org
into your recipients
Heiko
next parent reply other threads:[~2012-05-14 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1336572489-21457-1-git-send-email-daniel.lezcano@linaro.org>
[not found] ` <4FB048E4.8070405@linaro.org>
2012-05-14 8:52 ` Heiko Stübner [this message]
2012-05-14 8:57 ` [PATCH 0/2] ARM: S3C64xx: cpuidle cleanups Mark Brown
2012-05-14 9:22 ` Daniel Lezcano
2012-05-14 13:51 ` Kukjin Kim
2012-05-14 13:56 ` Daniel Lezcano
2012-05-14 13:44 ` Daniel Lezcano
2012-05-14 14:06 Daniel Lezcano
2012-05-17 6:57 ` Kukjin Kim
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=201205141052.47567.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=ben-linux@fluff.org \
--cc=daniel.lezcano@linaro.org \
--cc=kgene.kim@samsung.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.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