public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Michal Marek <mmarek@suse.cz>,
	linux-arch@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kbuild@vger.kernel.org,
	Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: kbuild: fixing the select problem
Date: Thu, 06 May 2010 16:05:56 -0500	[thread overview]
Message-ID: <1273179956.2881.23.camel@mulgrave.site> (raw)
In-Reply-To: <20100506135952.eeb0e4c5.randy.dunlap@oracle.com>

On Thu, 2010-05-06 at 13:59 -0700, Randy Dunlap wrote:
> On Thu, 06 May 2010 15:48:35 -0500 James Bottomley wrote:
> 
> > On Thu, 2010-05-06 at 09:52 -0500, James Bottomley wrote:
> > > The list is
> > > 
> > > USB_ARCH_HAS_HCD has 4 defaults
> > > DEFCONFIG_LIST has 5 defaults
> > > MAC80211_RC_DEFAULT has 2 defaults
> > > X86_L1_CACHE_SHIFT has 2 defaults
> > > SPLIT_PTLOCK_CPUS has 2 defaults
> > > X86_MINIMUM_CPU_FAMILY has 3 defaults
> > > DEFAULT_TCP_CONG has 2 defaults
> > > DEFCONFIG_LIST has 5 defaults
> > > USB_ARCH_HAS_HCD has 4 defaults
> > > X86_L1_CACHE_SHIFT has 2 defaults
> > > X86_MINIMUM_CPU_FAMILY has 3 defaults
> > > SPLIT_PTLOCK_CPUS has 2 defaults
> > > DEFAULT_TCP_CONG has 2 defaults
> > > MAC80211_RC_DEFAULT has 2 defaults
> > 
> > Here's a patch that alters the default processing to the needed form and
> > checks the old vs new values.  I've been running randconfigs but I can't
> > get the warning to trip ... have at it.
> > 
> 
> I don't see the warning, but I took a problem config from linux-next 2010-0506
> (today) [attached].  In it, CONFIG_TCG_BIOS_LOG=y and that selects ACPI,
> so now ACPI is enabled, but ACPI depends on PM and PCI, but they are still not
> selected...
> 
> or is this only step 1 of a multi-step implementation?

Actually, it's not any step.  It's just validation of the contention
that I can alter the default parser from taking the first valid default
to calculating the or of the defaults without changing the current
kbuild behaviour.

The patch to fix kbuild goes on top of this change minus the warnings
(when I actually code it up).

James

  reply	other threads:[~2010-05-06 21:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 21:49 kbuild: fixing the select problem James Bottomley
2010-05-05 21:49 ` James Bottomley
2010-05-06  6:47 ` Geert Uytterhoeven
2010-05-06  6:47   ` Geert Uytterhoeven
2010-05-06 13:17   ` James Bottomley
2010-05-06 13:17     ` James Bottomley
2010-05-06 13:36     ` Geert Uytterhoeven
2010-05-06 16:47     ` Valdis.Kletnieks
2010-05-06 16:47       ` Valdis.Kletnieks
2010-05-06 17:25       ` Geert Uytterhoeven
2010-05-06 17:25         ` Geert Uytterhoeven
2010-05-06 14:24 ` Michal Marek
2010-05-06 14:24   ` Michal Marek
2010-05-06 14:52   ` James Bottomley
2010-05-06 14:52     ` James Bottomley
2010-05-06 20:48     ` James Bottomley
2010-05-06 20:59       ` Randy Dunlap
2010-05-06 21:05         ` James Bottomley [this message]
2010-05-06 16:52   ` Vegard Nossum
2010-05-07 11:31 ` Catalin Marinas

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=1273179956.2881.23.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.org \
    --cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox