From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Rfkill rewrite
Date: Sat, 18 Jul 2009 19:40:02 +0200 [thread overview]
Message-ID: <1247938802.18391.0.camel@johannes.local> (raw)
In-Reply-To: <4A61EE43.4060003@tuffmail.co.uk>
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
On Sat, 2009-07-18 at 16:46 +0100, Alan Jenkins wrote:
> It seems my GCC has a stronger definition of "must" than you do :-).
> I can't get rid of the warning by casting it to void. So I'm not sure
> __must_check is really appropriate here.
Heh, my gcc agrees with you :)
I'm happy to remove it -- want to send a patch?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-18 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 15:46 Rfkill rewrite Alan Jenkins
2009-07-18 17:40 ` Johannes Berg [this message]
2009-07-18 18:20 ` [PATCH] rfkill: remove too-strict __must_check Alan Jenkins
2009-07-18 18:22 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2009-05-01 9:42 rfkill rewrite Alan Jenkins
2009-05-05 8:15 ` Johannes Berg
2009-05-05 14:04 ` Alan Jenkins
2009-05-05 14:11 ` Johannes Berg
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=1247938802.18391.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-wireless@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