From: Stephen Boyd <sboyd@codeaurora.org>
To: pageexec@freemail.hu
Cc: khali@linux-fr.org, rostedt@goodmis.org,
Behan Webster <behanw@converseincode.com>,
rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
dwmw2@infradead.org, Mark Charlebois <charlebm@gmail.com>
Subject: Re: [PATCH] module: LLVMLinux: Remove unused function warning from __param_check macro
Date: Fri, 07 Mar 2014 17:35:39 -0800 [thread overview]
Message-ID: <531A73EB.6060403@codeaurora.org> (raw)
In-Reply-To: <531A719C.19855.32E9C505@pageexec.freemail.hu>
On 03/07/14 17:25, PaX Team wrote:
> On 7 Mar 2014 at 16:52, Behan Webster wrote:
>
>> On 03/07/14 14:56, PaX Team wrote:
>>> why can't you have the attr on the definition itself:
>>>
>>> static inline __unused type *__check_##name(void) { return(p); }
>>>
>>>
>>>
>> "__unused" isn't defined anywhere I can find, except in:
>>
>> src/linux/drivers/net/ethernet/amd/declance.c:#define __unused
>> __attribute__ ((unused))
> oh i forgot about that, you'd of course place this #define
> into the appropriate compiler*.h files so that other code
> can make use of it in the future as well ;).
>
It looks like it already exists, __always_unused.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-03-08 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 19:08 [PATCH] module: LLVMLinux: Remove unused function warning from __param_check macro behanw
2014-03-07 22:56 ` PaX Team
2014-03-08 0:52 ` Behan Webster
2014-03-08 1:25 ` PaX Team
2014-03-08 1:35 ` Stephen Boyd [this message]
2014-03-08 2:10 ` [PATCH v2] " behanw
2014-03-08 2:17 ` Joe Perches
2014-03-08 2:21 ` Behan Webster
2014-03-11 6:11 ` [PATCH] " Rusty Russell
2014-03-11 7:00 ` Behan Webster
2014-03-11 21:24 ` [PATCH v3] " behanw
2014-03-17 2:47 ` Rusty Russell
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=531A73EB.6060403@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=behanw@converseincode.com \
--cc=charlebm@gmail.com \
--cc=dwmw2@infradead.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
/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