From: Peter Korsgaard <jacmet@sunsite.dk>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Hilman, Kevin" <khilman@ti.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
"tony@atomide.com" <tony@atomide.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] ARM: OMAP4: cminst: Add boot time __init function for cminst
Date: Wed, 15 Feb 2012 08:40:37 +0100 [thread overview]
Message-ID: <87mx8ktuh6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A8317CF3B2@DBDE01.ent.ti.com> (Vaibhav Hiremath's message of "Wed, 15 Feb 2012 06:27:53 +0000")
>>>>> "Vaibhav" == Hiremath, Vaibhav <hvaibhav@ti.com> writes:
Hi,
Vaibhav> - BUG_ON(part >= OMAP4_MAX_PRCM_PARTITIONS ||
Vaibhav> + BUG_ON(part >= max_cm_partitions ||
Vaibhav> part == OMAP4430_INVALID_PRCM_PARTITION ||
>>
>> How about dropping the OMAP4430_ prefix here as it's no longer 4430 specific?
>>
Vaibhav> Peter,
Vaibhav> You could be right here, from this patch perspective, this
Vaibhav> change doesn't make sense.
Vaibhav> But at the first place I am quite not sure, why this has been
Vaibhav> named as OMAP4430_? Vs some macros are named as OMAP4_.
Vaibhav> So first we need to understand why it has been named this way,
Vaibhav> may be "Paul Walmsley" can comment on this. He is original
Vaibhav> author of this file.
As I read it, it doesn't have anything to do with any specific hardware,
it's just to catch bugs when people forget to initialize the structure
field:
arch/arm/mach-omap2/prcm44xx.h:
/*
* OMAP4 PRCM partition IDs
*
* The numbers and order are arbitrary, but 0 is reserved for the
* 'invalid' partition in case someone forgets to add a
* .prcm_partition field.
*/
#define OMAP4430_INVALID_PRCM_PARTITION 0
--
Bye, Peter Korsgaard
WARNING: multiple messages have this Message-ID (diff)
From: jacmet@sunsite.dk (Peter Korsgaard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP4: cminst: Add boot time __init function for cminst
Date: Wed, 15 Feb 2012 08:40:37 +0100 [thread overview]
Message-ID: <87mx8ktuh6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A8317CF3B2@DBDE01.ent.ti.com> (Vaibhav Hiremath's message of "Wed, 15 Feb 2012 06:27:53 +0000")
>>>>> "Vaibhav" == Hiremath, Vaibhav <hvaibhav@ti.com> writes:
Hi,
Vaibhav> - BUG_ON(part >= OMAP4_MAX_PRCM_PARTITIONS ||
Vaibhav> + BUG_ON(part >= max_cm_partitions ||
Vaibhav> part == OMAP4430_INVALID_PRCM_PARTITION ||
>>
>> How about dropping the OMAP4430_ prefix here as it's no longer 4430 specific?
>>
Vaibhav> Peter,
Vaibhav> You could be right here, from this patch perspective, this
Vaibhav> change doesn't make sense.
Vaibhav> But at the first place I am quite not sure, why this has been
Vaibhav> named as OMAP4430_? Vs some macros are named as OMAP4_.
Vaibhav> So first we need to understand why it has been named this way,
Vaibhav> may be "Paul Walmsley" can comment on this. He is original
Vaibhav> author of this file.
As I read it, it doesn't have anything to do with any specific hardware,
it's just to catch bugs when people forget to initialize the structure
field:
arch/arm/mach-omap2/prcm44xx.h:
/*
* OMAP4 PRCM partition IDs
*
* The numbers and order are arbitrary, but 0 is reserved for the
* 'invalid' partition in case someone forgets to add a
* .prcm_partition field.
*/
#define OMAP4430_INVALID_PRCM_PARTITION 0
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-02-15 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 15:29 [PATCH 0/2] ARM: OMAP4: Cleanup in cminst code Vaibhav Hiremath
2012-02-14 15:29 ` Vaibhav Hiremath
2012-02-14 15:29 ` [PATCH 1/2] ARM: OMAP4: cminst: Add boot time __init function for cminst Vaibhav Hiremath
2012-02-14 15:29 ` Vaibhav Hiremath
2012-02-14 21:11 ` Peter Korsgaard
2012-02-14 21:11 ` Peter Korsgaard
2012-02-15 6:27 ` Hiremath, Vaibhav
2012-02-15 6:27 ` Hiremath, Vaibhav
2012-02-15 7:40 ` Peter Korsgaard [this message]
2012-02-15 7:40 ` Peter Korsgaard
2012-02-14 15:29 ` [PATCH 2/2] ARM: OMAP: am33xx: Hook-up am33xx support to existing cm code Vaibhav Hiremath
2012-02-14 15:29 ` Vaibhav Hiremath
2012-02-14 20:55 ` Peter Korsgaard
2012-02-14 20:55 ` Peter Korsgaard
2012-02-15 6:28 ` Hiremath, Vaibhav
2012-02-15 6:28 ` Hiremath, Vaibhav
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=87mx8ktuh6.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=b-cousson@ti.com \
--cc=hvaibhav@ti.com \
--cc=khilman@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 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.