[PATCH] Remove ARM default configurations which duplicate omap3_defconfig

[Tony Lindgren]

* Vincent Sanders <vince at kyllikki.org> [100804 13:59]:
> On Wed, Aug 04, 2010 at 08:35:36AM +0300, Tony Lindgren wrote:
> > * Vincent Sanders <vince at simtec.co.uk> [100803 23:23]:
> > > These configurations are no longer useful as the systems they support
> > > are covered by the generic omap3_defconfig
> > 
> > Since the defconfigs will stay around at least for a while
> > in the compacted form..
> 
> The default configuration situation is simply insane there are over
> 170 of them for crying out loud. We *need* to reduce the number to
> sane levels or Linus will simply rm the lot.

I agree it's out of control. 
 
> > .. And until we have sorted out how to deal with which drivers
> > need to be compiled in or as modules for each board, I'd
> > rather keep these defconfigs around for now.
> > 
> 
> > Can we just disable building these with some blacklist
> > in Kautobuild?
> > 
> 
> There is no such thing, the point was to reduce the number of configurations.

I would like to reduce the configs too, but the issue of knowing
which drivers and modules to build is still unhandled unfortunately.
 
> > > Signed-off-by:Vincent Sanders <vince at simtec.co.uk>
> > > Acked-by:Tony Lindgren <tony at atomide.com>
> > 
> > So Not-yet-acked-by until some Kconfig issues are sorted out :)
> > 
> 
> I obviously misinterpreted your ack in your previous mail. 

Yes sorry about that.
 
> I give up, really, its completely pointless to carry on even trying to
> make this situation better, noone else really cares so...  

I do, I'm having the same problem just building the omap configs
on my box!
 
> I am on holiday for a few weeks so will not be moderating the lists or
> running the autobuilder for that time. If on my return I feel like it
> I may turn kautobuild back on but probably not.

Happy vacation & thanks for all the hard work. Hopefully we can still
have kautobuild.. If you really insist on removing these defconfigs
to keep kautobuild going, I'm cool with that. That still does not
solve the remaining issue though on how to know the drivers and modules
needed for each board.

Regards,

Tony