On Thu, 25 Oct 2007 04:06:13 -0400 (EDT)
Jeff Garzik <jeff@garzik.org> wrote:

quoted text
> 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.
> 

it would be nice if we could have this always-on for external modules,
so that people who're developing new modules realize from the start
that they're using API's they shouldn't, no matter what config option
they (or their distro) picked...


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
-
unsubscribe notice
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/