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
[email protected] never heard a horse sing a song.
Silicon Graphics, Inc. -- Louis Armstrong
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
