From: Arjan van de Ven <arjan@infradead.org>
To: David Brownell <david-b@pacbell.net>
Cc: Jeff Garzik <jeff@garzik.org>,
dbrownell@users.sourceforge.net, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SPI: improve sysfs compiler complaint handling
Date: Thu, 12 Oct 2006 20:39:34 +0200 [thread overview]
Message-ID: <1160678375.3000.454.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200610121108.59727.david-b@pacbell.net>
> Does anyone know why the GCC folk have decided to go against decades
> of common practice here???
because it's new semantics. I was involved in this GCC feature (not in
the coding just in the asking for it) and this behavior was specifically
requested: It is called __must_check, you MUST CHECK it. It's not the
normal "unused warning", by putting the attribute on the function you
tell gcc that the result MUST be checked. Just a cast to void isn't
checking it.... so it rightfully warns.
next prev parent reply other threads:[~2006-10-12 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 1:49 Jeff Garzik
2006-10-12 18:08 ` David Brownell
2006-10-12 18:24 ` Andrew Morton
2006-10-12 18:46 ` David Brownell
2006-10-12 19:08 ` Arjan van de Ven
2006-10-12 18:39 ` Arjan van de Ven [this message]
2006-10-12 19:07 ` David Brownell
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=1160678375.3000.454.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=dbrownell@users.sourceforge.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®