mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brent Casavant <bcasavan@sgi.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Jeremy Higdon <jeremy@sgi.com>, Pat Gefre <pfg@sgi.com>
Subject: Re: [PATCH 2/2] ioc4: Enable build on non-SN2
Date: Tue, 10 Oct 2006 14:06:30 -0500 (CDT)	[thread overview]
Message-ID: <20061010140429.O71367@pkunk.americas.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0610102042290.17718@yvahk01.tjqt.qr>

On Tue, 10 Oct 2006, Jan Engelhardt wrote:

> >> Mostly curious:  did you observe that this is required?
> >> I always thought that Roman said that unknown config variables
> >> caused a rescan by kconfig.  IOW, I thought that it wouldn't
> >> be observable by a user.  Just wondering..
> >
> >If it causes a rescan (I don't rightly know) it must have changed.
> >I caught a bit of flak for an incorrectly ordered config statement
> >once before, but that was a few years ago.
> 
> I am sure it causes a rescan, because activating 
> CONFIG_NETFILTER for example makes some options available that are 
> defined before NETFILTER, such as IP_ROUTE_FWMARK, IP_VS, 
> NETFILTER_XT_TARGET_CONNMARK and NETFILTER_XT_TARGET_NOTRACK, and 
> activating NETFILTER _will_ cause a rescan with `make oldconfig` - I 
> just tried. (Things are a little different with menuconfig/xconfig and 
> such of course)

In my case I think it was the menuconfig or xconfig that someone
complained about (I don't rightly remember which one).  In any case,
for the patch at hand, I could find no particular reason that
the drivers/misc Kconfig line couldn't be moved up to preserve peace
and harmony.

Brent

-- 
Brent Casavant                          All music is folk music.  I ain't
bcasavan@sgi.com                        never heard a horse sing a song.
Silicon Graphics, Inc.                    -- Louis Armstrong

  reply	other threads:[~2006-10-10 19:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 17:11 Brent Casavant
2006-10-10 17:39 ` Randy Dunlap
2006-10-10 18:21   ` Brent Casavant
2006-10-10 18:53     ` Jan Engelhardt
2006-10-10 19:06       ` Brent Casavant [this message]
2006-10-10 19:06       ` Randy Dunlap
2006-10-10 18:26   ` Brent Casavant
2006-10-12  0:23 ` Andrew Morton
2006-10-12 17:16   ` Brent Casavant
2006-10-12 19:37   ` Brent Casavant

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=20061010140429.O71367@pkunk.americas.sgi.com \
    --to=bcasavan@sgi.com \
    --cc=akpm@osdl.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jeremy@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pfg@sgi.com \
    --cc=rdunlap@xenotime.net \
    /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

all inboxes | Powered by JetHome®