linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Remove ARM default configurations which duplicate omap3_defconfig
Date: Wed, 4 Aug 2010 14:25:46 +0300	[thread overview]
Message-ID: <20100804112546.GM9881@atomide.com> (raw)
In-Reply-To: <20100804110130.GA30181@kyllikki.org>

* Vincent Sanders <vince@kyllikki.org> [100804 13:59]:
> On Wed, Aug 04, 2010 at 08:35:36AM +0300, Tony Lindgren wrote:
> > * Vincent Sanders <vince@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@simtec.co.uk>
> > > Acked-by:Tony Lindgren <tony@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

  reply	other threads:[~2010-08-04 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 20:19 [PATCH] Remove ARM default configurations which duplicate omap3_defconfig Vincent Sanders
2010-08-04  5:35 ` Tony Lindgren
2010-08-04 11:01   ` Vincent Sanders
2010-08-04 11:25     ` Tony Lindgren [this message]
2010-08-04 11:30   ` Russell King - ARM Linux
2010-08-04 12:35     ` Tony Lindgren

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=20100804112546.GM9881@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).