On Monday 13 October 2008, Peter 'p2' De Schrijver wrote:
> > > +extern struct twl4030_power_data generic3430_t2scripts_data;
> >
> > Such "extern" decls should as a rule be in header files...
> >
> > In this case the rule is appropriate, since you've got the
> > same decl in three different plac
Make omap3 evm, beagle and overo use the generic twl4030 script.
Signed-off-by: Peter 'p2' De Schrijver <[EMAIL PROTECTED]>
---
arch/arm/mach-omap2/Makefile|9 ++---
arch/arm/mach-omap2/board-omap3beagle.c |4 ++--
arch/arm/mach-omap2/board-omap3evm.c|4 ++--
arch/
On Fri, Oct 10, 2008 at 10:50:29AM -0700, ext David Brownell wrote:
> On Friday 10 October 2008, Peter 'p2' De Schrijver wrote:
> > +extern struct twl4030_power_data generic3430_t2scripts_data;
>
> Such "extern" decls should as a rule be in header files...
>
> In this case the rule is appropriate
On Friday 10 October 2008, Peter 'p2' De Schrijver wrote:
> +extern struct twl4030_power_data generic3430_t2scripts_data;
Such "extern" decls should as a rule be in header files...
In this case the rule is appropriate, since you've got the
same decl in three different places. That's about two ti
Make omap3 evm, beagle and overo use the generic twl4030 script.
Signed-off-by: Peter 'p2' De Schrijver <[EMAIL PROTECTED]>
---
arch/arm/mach-omap2/Makefile|9 ++---
arch/arm/mach-omap2/board-omap3beagle.c |3 +++
arch/arm/mach-omap2/board-omap3evm.c|3 +++
arch/ar