From: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Wang Dongsheng-B40534 <B40534@freescale.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
Scott Wood <scottwood@freescale.com>,
"preeti@linux.vnet.ibm.com" <preeti@linux.vnet.ibm.com>,
"linux-pm@lists.linux-foundation.org"
<linux-pm@lists.linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [RFC PATCH V3 3/5] powerpc/cpuidle: Generic powerpc backend cpuidle driver.
Date: Thu, 22 Aug 2013 12:11:12 +0530 [thread overview]
Message-ID: <5215B288.7040609@linux.vnet.ibm.com> (raw)
In-Reply-To: <1377151097.25016.287.camel@pasglop>
On 08/22/2013 11:28 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-08-22 at 11:20 +0530, Deepthi Dharwar wrote:
>> But if having cpuidle backend-driver separately for other powerpc arcs
>> makes sense such that each one have their own state information etc
>> then it makes sense to name the files as cpuidle-power.c,
>> cpuilde-ppc32.c and so on.
>
> If by "power" you mean IBM POWER machines/CPUs, then make it
> cpuidle-ibm-power or cpuidle-book3s64 maybe to clarify what families it
> affects.
Sure. Thanks :)
Regards,
Deepthi
> Cheers
> Ben.
>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
>
next prev parent reply other threads:[~2013-08-22 6:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 4:27 [RFC PATCH V3 0/5] powerpc/cpuidle: Generic POWERPC cpuidle driver enabled for POWER and POWERNV platforms Deepthi Dharwar
2013-08-19 4:28 ` [RFC PATCH V3 1/5] pseries/cpuidle: Remove dependency of pseries.h file Deepthi Dharwar
2013-08-19 4:28 ` [RFC PATCH V3 2/5] pseries: Move plpar_wrapper.h to powerpc common include/asm location Deepthi Dharwar
2013-08-19 4:28 ` [RFC PATCH V3 3/5] powerpc/cpuidle: Generic powerpc backend cpuidle driver Deepthi Dharwar
2013-08-19 5:52 ` Wang Dongsheng-B40534
2013-08-19 10:18 ` Deepthi Dharwar
2013-08-19 18:17 ` Scott Wood
2013-08-21 4:53 ` Deepthi Dharwar
2013-08-21 20:08 ` Scott Wood
2013-08-22 5:50 ` Deepthi Dharwar
2013-08-22 5:58 ` Benjamin Herrenschmidt
2013-08-22 6:41 ` Deepthi Dharwar [this message]
2013-08-22 21:24 ` Scott Wood
2013-08-23 10:11 ` Deepthi Dharwar
2013-08-19 4:28 ` [RFC PATCH V3 4/5] powerpc/cpuidle: Enable powernv cpuidle support Deepthi Dharwar
2013-08-19 4:28 ` [RFC PATCH V3 5/5] powernv/cpuidle: Enable idle powernv cpu to call into the cpuidle framework Deepthi Dharwar
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=5215B288.7040609@linux.vnet.ibm.com \
--to=deepthi@linux.vnet.ibm.com \
--cc=B07421@freescale.com \
--cc=B40534@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=scottwood@freescale.com \
/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.