From: Randy Dunlap <rdunlap@xenotime.net>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Brent Casavant <bcasavan@sgi.com>,
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 12:06:33 -0700 [thread overview]
Message-ID: <20061010120633.895c6dc7.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0610102042290.17718@yvahk01.tjqt.qr>
On Tue, 10 Oct 2006 20:53:39 +0200 (MEST) 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)
>
> >> The lines under ---help--- should be indented by 2 spaces (by
> >> convention) (and even though they were not when in the /sn/ subdir).
> >
> >Thanks for catching that... I just blindly copied from one spot
> >to another. I'll resend.
>
> Not tabs?
One tab + 2 spaces. Or 2 spaces more than the rest of
the config entry.
---
~Randy
next prev parent reply other threads:[~2006-10-10 19:05 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
2006-10-10 19:06 ` Randy Dunlap [this message]
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=20061010120633.895c6dc7.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=bcasavan@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jeremy@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.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
all inboxes | Powered by JetHome®