From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: attribute warn_unused_result
Date: Tue, 07 Sep 2004 22:23:22 +1000 [thread overview]
Message-ID: <413DA83A.7010704@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
Gcc3.4.1 has recently been complaining of a number of unused results
from function with attribute warn_unused_result set. I'm not sure of how
you want to tackle this so I'm avoiding posting patches. Should we
remove the attribute (seems the likely option) or set some dummy
variable (sounds stupid now that I ask it).
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2004-09-07 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 12:23 Con Kolivas [this message]
2004-09-07 12:38 ` attribute warn_unused_result Arjan van de Ven
2004-09-07 12:43 ` Con Kolivas
2004-09-07 12:47 ` Arjan van de Ven
2004-09-07 12:53 ` Con Kolivas
2004-09-07 13:04 ` Con Kolivas
2004-09-07 14:10 ` Jesper Juhl
2004-09-07 13:08 ` Jesper Juhl
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=413DA83A.7010704@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.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 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.