From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-scsi@vger.kernel.org, Greg KH <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Illustration of warning explosion silliness
Date: Thu, 28 Sep 2006 19:18:22 -0400 [thread overview]
Message-ID: <451C583E.8090501@garzik.org> (raw)
In-Reply-To: <20060927203417.f07674de.akpm@osdl.org>
Andrew Morton wrote:
> There, I feel better now. If you want to see the other warnings, set
> CONFIG_ENABLE_MUST_CHECK=n.
While Googling around for Hobson's Choice[1], I realized that we are
presented with the utterly apropos Morton's Fork:
http://en.wikipedia.org/wiki/Morton's_Fork
With CONFIG_ENABLE_MUST_CHECK warning explosion, we must choose between
seeing warnings in our own code, but missing __must_check bugs, and
seeing all the __must_check bugs but obscuring our own day-to-day devel
problems.
In the future, I would hope that it would be reasonable to merge a
feature like this along with the cleanups that avoid a warning explosion.
Jeff
[1] http://en.wikipedia.org/wiki/Hobson's_choice
prev parent reply other threads:[~2006-09-28 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 0:58 [PATCH] Illustration of warning explosion silliness Jeff Garzik
2006-09-28 1:35 ` Andrew Morton
2006-09-28 1:48 ` Jeff Garzik
2006-09-28 3:34 ` Andrew Morton
2006-09-28 4:19 ` Jeff Garzik
2006-09-28 4:36 ` Andrew Morton
2006-09-28 4:42 ` Jeff Garzik
2006-09-28 4:47 ` Andrew Morton
2006-09-28 4:44 ` Andrew Morton
2006-09-28 4:54 ` Jeff Garzik
2006-09-28 5:04 ` Andrew Morton
2006-09-28 23:18 ` Jeff Garzik [this message]
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=451C583E.8090501@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox