From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: LKML <linux-kernel@vger.kernel.org>, torvalds@linux-foundation.org
Subject: Re: [PATCH] Permit silencing of __deprecated warnings.
Date: Thu, 25 Oct 2007 01:15:16 -0700 [thread overview]
Message-ID: <20071025011516.aea17222.akpm@linux-foundation.org> (raw)
In-Reply-To: <41621d56a0a0e4e5f861e1725f18990df5e927ad.1193299380.git.jeff@garzik.org>
On Thu, 25 Oct 2007 04:06:13 -0400 (EDT) Jeff Garzik <jeff@garzik.org> 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?
next prev parent reply other threads:[~2007-10-25 8:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 8:06 [PATCH] sound/oss/sb_common.c: fix casting warning Jeff Garzik
2007-10-25 8:06 ` [PATCH] Permit silencing of __deprecated warnings Jeff Garzik
2007-10-25 8:15 ` Andrew Morton [this message]
2007-10-25 8:20 ` Jeff Garzik
2007-10-25 15:34 ` Linus Torvalds
2007-10-25 11:02 ` Sam Ravnborg
2007-10-26 3:07 ` Arjan van de Ven
2007-10-25 8:06 ` [PATCH] Remove #warnings for longstanding conditions Jeff Garzik
2007-10-25 9:52 ` Karsten Keil
2007-10-25 11:22 ` Matthew Wilcox
2007-10-26 2:07 ` Jeff Garzik
2007-10-26 2:14 ` Matthew Wilcox
2007-10-26 2:19 ` Jeff Garzik
2007-10-25 8:06 ` [PATCH] ISDN/capidrv: fix casting warning Jeff Garzik
2007-10-25 9:51 ` Karsten Keil
2007-10-26 0:53 ` Jeff Garzik
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=20071025011516.aea17222.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.