From: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Len Brown <lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
nsekhar-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH 0/4] davinci: cpuidle - some cleanups
Date: Mon, 04 Feb 2013 13:08:31 +0100 [thread overview]
Message-ID: <510FA4BF.7050001@linaro.org> (raw)
In-Reply-To: <510C0E4E.3010008-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On 02/01/2013 07:49 PM, Len Brown wrote:
> 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.
Are you ok if I take care of that ?
-- 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
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
prev parent reply other threads:[~2013-02-04 12:08 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 ` [PATCH 0/4] davinci: cpuidle - some cleanups Len Brown
2013-02-03 11:54 ` 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 [this message]
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=510FA4BF.7050001@linaro.org \
--to=daniel.lezcano-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nsekhar-l0cyMroinI0@public.gmane.org \
--cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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).