Paul Walmsley writes:
> On Tue, 12 May 2009, Kevin Hilman wrote:
>
>> As the OMAP4 patches are coming in, there seems to be a bit of variety
>> in the naming of functions/macros/variables etc.
>>
>> Could I propose that we just use omap4_* and OMAP4_* instead of
>> OMAP44XX_* or OMAP4_* etc.
On Tue, 12 May 2009, Kevin Hilman wrote:
> As the OMAP4 patches are coming in, there seems to be a bit of variety
> in the naming of functions/macros/variables etc.
>
> Could I propose that we just use omap4_* and OMAP4_* instead of
> OMAP44XX_* or OMAP4_* etc.
>
> I know that OMAP2 and OMAP
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Tuesday, May 12, 2009 8:29 PM
> To: linux-omap@vger.kernel.org
> Cc: Shilimkar, Santosh
> Subject: OMAP4 naming conventions
>
> As the OMAP4 patches are coming in, there seem
; Cc: Shilimkar, Santosh
> > Subject: OMAP4 naming conventions
> >
> > As the OMAP4 patches are coming in, there seems to be a bit of variety
> > in the naming of functions/macros/variables etc.
> >
> > Could I propose that we just use omap4_* and OMAP4_* instead of
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org
> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Kevin Hilman
> Sent: Tuesday, May 12, 2009 8:29 PM
> To: linux-omap@vger.kernel.org
> Cc: Shilimkar, Santosh
> Subject: OMAP4 naming conventions
>
As the OMAP4 patches are coming in, there seems to be a bit of variety
in the naming of functions/macros/variables etc.
Could I propose that we just use omap4_* and OMAP4_* instead of
OMAP44XX_* or OMAP4_* etc.
I know that OMAP2 and OMAP3 have a variety of forms here too, but
those should pro
