On Thu, 25 Oct 2007 04:06:13 -0400 (EDT) Jeff Garzik <[EMAIL PROTECTED]> wrote:
> The __deprecated marker is quite useful in highlighting the remnants of > old APIs that want removing. > > However, it is quite normal for one or more years to pass, before the > (usually ancient, bitrotten) code in question is either updated or > deleted. > > Thus, like __must_check, add a Kconfig option that permits the silencing > of this compiler warning. > > This change mimics the ifdef-ery and Kconfig defaults of MUST_CHECK as > closely as possible. Sigh. Can't we just fix the dud code? Or mark it BROKEN and see what happens? - 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/
