From: Kukjin Kim <kgene.kim@samsung.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
ben-linux@fluff.org, kgene.kim@samsung.com,
linux-arm-kernel@lists.infradead.org,
linaro-dev@lists.linaro.org, patches@linaro.org,
linux-samsung-soc@vger.kernel.org, heiko@sntech.de
Subject: Re: [PATCH 1/2] ARM: s3c64xx: cpuidle - declare the states with the new api
Date: Sun, 20 May 2012 02:35:05 +0900 [thread overview]
Message-ID: <4FB7D9C9.1020004@samsung.com> (raw)
In-Reply-To: <20120517122802.GG26337@opensource.wolfsonmicro.com>
On 05/17/12 21:28, Mark Brown wrote:
> On Mon, May 14, 2012 at 04:06:16PM +0200, Daniel Lezcano wrote:
>> The states are now part of the cpuidle_driver structure, so we can
>> declare the states in this structure directly. That saves us an extra
>> variable declaration and a memcpy.
>
> Tested-by: Mark Brown<broonie@opensource.wolfsonmicro.com>
Thanks for testing, applied this series.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: s3c64xx: cpuidle - declare the states with the new api
Date: Sun, 20 May 2012 02:35:05 +0900 [thread overview]
Message-ID: <4FB7D9C9.1020004@samsung.com> (raw)
In-Reply-To: <20120517122802.GG26337@opensource.wolfsonmicro.com>
On 05/17/12 21:28, Mark Brown wrote:
> On Mon, May 14, 2012 at 04:06:16PM +0200, Daniel Lezcano wrote:
>> The states are now part of the cpuidle_driver structure, so we can
>> declare the states in this structure directly. That saves us an extra
>> variable declaration and a memcpy.
>
> Tested-by: Mark Brown<broonie@opensource.wolfsonmicro.com>
Thanks for testing, applied this series.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2012-05-19 17:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 14:06 [PATCH 0/2] ARM: S3C64xx: cpuidle cleanups Daniel Lezcano
2012-05-14 14:06 ` Daniel Lezcano
2012-05-14 14:06 ` [PATCH 1/2] ARM: s3c64xx: cpuidle - declare the states with the new api Daniel Lezcano
2012-05-14 14:06 ` Daniel Lezcano
2012-05-17 7:02 ` Kukjin Kim
2012-05-17 7:02 ` Kukjin Kim
2012-05-17 12:28 ` Mark Brown
2012-05-17 12:28 ` Mark Brown
2012-05-19 17:35 ` Kukjin Kim [this message]
2012-05-19 17:35 ` Kukjin Kim
[not found] ` <1337004377-17732-1-git-send-email-daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-05-14 14:06 ` [PATCH 2/2] ARM: s3c64xx: cpuidle - use timekeeping wrapper Daniel Lezcano
2012-05-14 14:06 ` Daniel Lezcano
2012-05-17 12:28 ` Mark Brown
2012-05-17 12:28 ` Mark Brown
2012-05-17 6:57 ` [PATCH 0/2] ARM: S3C64xx: cpuidle cleanups Kukjin Kim
2012-05-17 6:57 ` Kukjin Kim
-- strict thread matches above, loose matches on Subject: below --
2012-05-09 14:08 Daniel Lezcano
2012-05-09 14:08 ` [PATCH 1/2] ARM: s3c64xx: cpuidle - declare the states with the new api 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=4FB7D9C9.1020004@samsung.com \
--to=kgene.kim@samsung.com \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=daniel.lezcano@linaro.org \
--cc=heiko@sntech.de \
--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 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.