From: Len Brown <lenb@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: nsekhar@ti.com, khilman@ti.com, patches@linaro.org,
linaro-dev@lists.linaro.org,
davinci-linux-open-source@linux.davincidsp.com,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 0/4] davinci: cpuidle - some cleanups
Date: Fri, 01 Feb 2013 13:49:50 -0500 [thread overview]
Message-ID: <510C0E4E.3010008@kernel.org> (raw)
In-Reply-To: <1359726495-8024-1-git-send-email-daniel.lezcano@linaro.org>
On 02/01/2013 08:48 AM, Daniel Lezcano wrote:
> This patchset does some cleanup. It could have been folded in a single
> patch but the review would have been less clean than splitting it into
> small and trivial patches.
>
> The main purpose of this patch is to remove the usage of the driver_data
> field from the state_usage structure. Len Brown is doing this cleanup in
> the intel_idle.c file. With this patchset, the processor_idle.c file will
> be the last user of this field.
Daniel,
Thanks for this cleanup.
Hopefully we can hear from somebody with davinci HW who can test it?
Looks like it is now up to me to address processor_idle.c and
finish the job of expunging driver_data.
thanks,
-Len Brown
Intel Open Source Technology Center
>
> Also, the patchset simplify the code and makes it a bit more clear to read.
>
> I don't have this hardware, the code is not tested.
>
> Daniel Lezcano (4):
> davinci: cpuidle - use global variable for ddr2 flag
> davinci: cpuidle - move code to prevent forward declaration
> davinci: cpuidle - remove the ops
> davinci: cpuidle - remove useless initialization
>
> arch/arm/mach-davinci/cpuidle.c | 84 ++++++++++++---------------------------
> 1 file changed, 25 insertions(+), 59 deletions(-)
>
next prev parent reply other threads:[~2013-02-01 18:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 13:48 [PATCH 0/4] davinci: cpuidle - some cleanups Daniel Lezcano
2013-02-01 13:48 ` [PATCH 1/4] davinci: cpuidle - use global variable for ddr2 flag Daniel Lezcano
2013-02-04 9:48 ` Sekhar Nori
2013-02-01 13:48 ` [PATCH 2/4] davinci: cpuidle - move code to prevent forward declaration Daniel Lezcano
[not found] ` <1359726495-8024-1-git-send-email-daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-02-01 13:48 ` [PATCH 3/4] davinci: cpuidle - remove the ops Daniel Lezcano
2013-02-01 13:48 ` [PATCH 4/4] davinci: cpuidle - remove useless initialization Daniel Lezcano
2013-02-01 18:49 ` Len Brown [this message]
2013-02-03 11:54 ` [PATCH 0/4] davinci: cpuidle - some cleanups Sekhar Nori
2013-02-03 12:22 ` Daniel Lezcano
2013-02-03 13:00 ` Sekhar Nori
2013-02-03 14:13 ` Daniel Lezcano
[not found] ` <510C0E4E.3010008-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2013-02-04 12:08 ` 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=510C0E4E.3010008@kernel.org \
--to=lenb@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=khilman@ti.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=nsekhar@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).