From: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-kernel@vger.kernel.org, preeti@linux.vnet.ibm.com,
srivatsa.bhat@linux.vnet.ibm.com, scottwood@freescale.com,
linux-pm@lists.linux-foundation.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V7 5/7] POWER/cpuidle: Generic POWER CPUIDLE driver supporting PSERIES.
Date: Thu, 07 Nov 2013 10:57:48 +0530 [thread overview]
Message-ID: <527B24D4.30009@linux.vnet.ibm.com> (raw)
In-Reply-To: <1383800462.4776.165.camel@pasglop>
On 11/07/2013 10:31 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-11-07 at 09:45 +0530, Deepthi Dharwar wrote:
>> 'powerpc' would be very generic arch and would comprise of all platforms
>> including embedded 32/64 bit to server 64 bit (similar to that of ARM).
>> This driver does not intend to support complete powerpc arch, but just
>> PSERIES and POWERNV platforms termed as 'POWER' processors. So to avoid
>> confusion btw 'power mgmt' and 'POWER' archs, I have prefixed both the
>> driver and file names with 'IBM'namely ibm-power-driver, cpuidle-ibm-power.
>
Hi Ben,
> Why not book3s ? powerpc-book3s ?
I went with 'ibm-power' thinking it would resolve the confusion,
but if ppl feel that is is good to get away from 'POWER' and have
powerpc-book3s instead to make things clearer, I am open for it.
Regards,
Deepthi
> That's what we use in other places to differenciate between the families
>
> Ben.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
michael@ellerman.id.au, scottwood@freescale.com,
srivatsa.bhat@linux.vnet.ibm.com, preeti@linux.vnet.ibm.com,
linux-pm@lists.linux-foundation.org, svaidy@linux.vnet.ibm.com
Subject: Re: [PATCH V7 5/7] POWER/cpuidle: Generic POWER CPUIDLE driver supporting PSERIES.
Date: Thu, 07 Nov 2013 10:57:48 +0530 [thread overview]
Message-ID: <527B24D4.30009@linux.vnet.ibm.com> (raw)
In-Reply-To: <1383800462.4776.165.camel@pasglop>
On 11/07/2013 10:31 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-11-07 at 09:45 +0530, Deepthi Dharwar wrote:
>> 'powerpc' would be very generic arch and would comprise of all platforms
>> including embedded 32/64 bit to server 64 bit (similar to that of ARM).
>> This driver does not intend to support complete powerpc arch, but just
>> PSERIES and POWERNV platforms termed as 'POWER' processors. So to avoid
>> confusion btw 'power mgmt' and 'POWER' archs, I have prefixed both the
>> driver and file names with 'IBM'namely ibm-power-driver, cpuidle-ibm-power.
>
Hi Ben,
> Why not book3s ? powerpc-book3s ?
I went with 'ibm-power' thinking it would resolve the confusion,
but if ppl feel that is is good to get away from 'POWER' and have
powerpc-book3s instead to make things clearer, I am open for it.
Regards,
Deepthi
> That's what we use in other places to differenciate between the families
>
> Ben.
>
>
next prev parent reply other threads:[~2013-11-07 5:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 11:01 [PATCH V7 0/7] POWER/cpuidle: Generic IBM-POWER cpuidle driver enabled for PSERIES and POWERNV platforms Deepthi Dharwar
2013-10-29 11:01 ` Deepthi Dharwar
2013-10-29 11:01 ` [PATCH V7 1/7] pseries/cpuidle: Move processor_idle.c to drivers/cpuidle Deepthi Dharwar
2013-10-29 11:01 ` Deepthi Dharwar
2013-11-06 20:58 ` Daniel Lezcano
2013-11-06 20:58 ` Daniel Lezcano
2013-10-29 11:01 ` [PATCH V7 2/7] pseries/cpuidle: Use cpuidle_register() for initialisation Deepthi Dharwar
2013-10-29 11:01 ` Deepthi Dharwar
2013-11-06 21:00 ` Daniel Lezcano
2013-11-06 21:00 ` Daniel Lezcano
2013-10-29 11:01 ` [PATCH V7 3/7] pseries/cpuidle: Make pseries_idle backend driver a non-module Deepthi Dharwar
2013-10-29 11:01 ` Deepthi Dharwar
2013-11-06 21:01 ` Daniel Lezcano
2013-11-06 21:01 ` Daniel Lezcano
2013-10-29 11:01 ` [PATCH V7 4/7] pseries/cpuidle: Remove MAX_IDLE_STATE macro Deepthi Dharwar
2013-10-29 11:01 ` Deepthi Dharwar
2013-11-06 21:02 ` Daniel Lezcano
2013-11-06 21:02 ` Daniel Lezcano
2013-10-29 11:01 ` [PATCH V7 5/7] POWER/cpuidle: Generic POWER CPUIDLE driver supporting PSERIES Deepthi Dharwar
2013-10-29 11:01 ` Deepthi Dharwar
2013-11-06 21:05 ` Daniel Lezcano
2013-11-06 21:05 ` Daniel Lezcano
2013-11-07 4:15 ` Deepthi Dharwar
2013-11-07 4:15 ` Deepthi Dharwar
2013-11-07 5:01 ` Benjamin Herrenschmidt
2013-11-07 5:01 ` Benjamin Herrenschmidt
2013-11-07 5:27 ` Deepthi Dharwar [this message]
2013-11-07 5:27 ` Deepthi Dharwar
2013-10-29 11:01 ` [PATCH V7 6/7] POWER/cpuidle: Enable powernv cpuidle support Deepthi Dharwar
2013-10-29 11:01 ` Deepthi Dharwar
2013-11-06 21:06 ` Daniel Lezcano
2013-11-06 21:06 ` Daniel Lezcano
2013-10-29 11:02 ` [PATCH V7 7/7] powernv/cpuidle: Enable idle powernv cpu to call into the cpuidle framework Deepthi Dharwar
2013-10-29 11:02 ` Deepthi Dharwar
2013-11-06 21:11 ` Daniel Lezcano
2013-11-06 21:11 ` 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=527B24D4.30009@linux.vnet.ibm.com \
--to=deepthi@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=scottwood@freescale.com \
--cc=srivatsa.bhat@linux.vnet.ibm.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.