Subject: Re: Rename all derived CONFIG variables
To: jgarzik@mandrakesoft.com (Jeff Garzik)
Date: Mon, 12 Mar 2001 14:24:28 +0000 (GMT)
Cc: kaos@ocs.com.au (Keith Owens), linux-kernel@vger.kernel.org,
        elenstev@mesatop.com, kbuild-devel@lists.sourceforge.net,
        alan@redhat.com (Alan Cox)
In-Reply-To: <3AAC79D1.F9837EE7@mandrakesoft.com> from "Jeff Garzik" at Mar 12, 2001 02:25:05 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E14cTFP-0001yS-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org

> Not only do I think that CONFIG_xxx_DERIVED needlessly extends the name
> of derived vars, but your patch does not belong in a stable series. 
> Derived CONFIG_xxx vars are likely to be referenced in source.  Changing
> those vars in the middle of a stable series pointlessly breaks external
> source code.
> 
> I hope vendors don't start applying this patch...

I dont see them doing that. I'm not going to be applying it for -ac either.
It would appear that this is a wrong way to fix the problem.

The config option checker should be scanning for define_*** options and
removing them from its output

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/