From: Kevin Hilman <khilman@deeprootsystems.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
tony@atomide.com, "Nayak, Rajendra" <rnayak@ti.com>
Subject: Re: [PATCH 11/14] OMAP4: PRCM: reorganize existing OMAP4 PRCM header files
Date: Wed, 08 Dec 2010 12:57:55 -0800 [thread overview]
Message-ID: <8739q8gey4.fsf@deeprootsystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1012072338130.13430@utopia.booyaka.com> (Paul Walmsley's message of "Tue, 7 Dec 2010 23:40:03 -0700 (MST)")
Paul Walmsley <paul@pwsan.com> writes:
> On Tue, 7 Dec 2010, Cousson, Benoit wrote:
>
>> On 12/7/2010 2:25 AM, Paul Walmsley wrote:
>>
>> [...]
>>
>> > + *
>> > + * XXX This file needs to be updated to align on one of "OMAP4",
>> > "OMAP44XX",
>> > + * or "OMAP4430".
>>
>> Yep, I was thinking to change that as well. My first thought was OMAP4 to get
>> a shorter name, but when we will introduce OMAP4440, we might have some new
>> entries, that will looks ugly close to OMAP4.
>> So at the end I will prefer OMAP44XX for the moment and we might renamed to
>> OMAP4430 or OMAP4440 for the entries that will diverge.
>>
>> Do you want to change that for 2.6.38?
>> It will require some sync with the various users of these defines, but that
>> should be doable.
>
> I don't mind waiting until after 2.6.38, I think we'll have a pretty huge
> pile of patches on our hands to merge already for .38... maybe Tony or
> Kevin have some opinions though.
I think this should wait 'til after 2.6.38, but be early in the next
cycle so all dependencies can be handled early.
Kevin
next prev parent reply other threads:[~2010-12-08 20:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 1:24 [PATCH 00/14] OMAP: PRCM/powerdomain/clockdomain patches for 2.6.38, part one Paul Walmsley
2010-12-07 1:25 ` [PATCH 01/14] OMAP: powerdomain: Move static allocations from powerdomains.h to a .c file Paul Walmsley
2010-12-07 1:25 ` [PATCH 02/14] OMAP: powerdomain: Infrastructure to put arch specific code Paul Walmsley
2010-12-07 1:25 ` [PATCH 03/14] OMAP: powerdomain: Arch specific funcs for state control Paul Walmsley
2010-12-07 1:25 ` [PATCH 04/14] OMAP: powerdomain: Arch specific funcs for logic control Paul Walmsley
2010-12-07 1:25 ` [PATCH 05/14] OMAP: powerdomain: Arch specific funcs for mem control Paul Walmsley
2010-12-07 1:25 ` [PATCH 06/14] OMAP4: powerdomain: Add pwrdm_clear_all_prev_pwrst Paul Walmsley
2010-12-07 1:25 ` [PATCH 07/14] OMAP2+: powerdomains: move powerdomain static data to .c files Paul Walmsley
2010-12-07 1:25 ` [PATCH 08/14] OMAP2+: clockdomains: move clockdomain " Paul Walmsley
2010-12-07 1:25 ` [PATCH 09/14] OMAP3: control/PRCM: add omap3_ctrl_write_boot_mode() Paul Walmsley
2010-12-07 1:25 ` [PATCH 10/14] OMAP3: control/PRCM: move CONTROL_PADCONF_SYS_NIRQ save/restore to SCM code Paul Walmsley
2010-12-07 1:25 ` [PATCH 11/14] OMAP4: PRCM: reorganize existing OMAP4 PRCM header files Paul Walmsley
2010-12-07 8:09 ` Cousson, Benoit
2010-12-08 6:47 ` Paul Walmsley
2010-12-09 22:31 ` Cousson, Benoit
2010-12-07 20:43 ` Cousson, Benoit
2010-12-08 6:40 ` Paul Walmsley
2010-12-08 20:57 ` Kevin Hilman [this message]
2010-12-07 1:25 ` [PATCH 12/14] OMAP4: PRCM: rename _MOD macros to _INST Paul Walmsley
2010-12-07 1:25 ` [PATCH 13/14] OMAP2/3: PRCM: split OMAP2/3-specific PRCM code into OMAP2/3-specific files Paul Walmsley
2010-12-07 13:37 ` Mark Brown
2010-12-15 4:50 ` Paul Walmsley
2010-12-15 12:23 ` Felipe Contreras
2010-12-22 3:51 ` Paul Walmsley
2010-12-15 16:39 ` Ramirez Luna, Omar
2010-12-22 4:10 ` Paul Walmsley
2010-12-07 1:25 ` [PATCH 14/14] OMAP3: PRM/CM: separate CM context save/restore; remove PRM context save/restore Paul Walmsley
2010-12-08 0:16 ` [PATCH 00/14] OMAP: PRCM/powerdomain/clockdomain patches for 2.6.38, part one Kevin Hilman
2010-12-08 6:20 ` Paul Walmsley
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=8739q8gey4.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=tony@atomide.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 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).