public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Li Zefan <lizf@cn.fujitsu.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: Fix to use unused attribute
Date: Thu, 29 Oct 2009 08:57:35 +0100	[thread overview]
Message-ID: <20091029075735.GC18976@elte.hu> (raw)
In-Reply-To: <4AE7A217.8030008@cn.fujitsu.com>


* Li Zefan <lizf@cn.fujitsu.com> wrote:

> ____ftrace_check_##name() is used for compile-time check
> on F_printk() only, so it should be marked as __unused
> instead of __used.
> 
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
> 
> I'm thinking about introducing __always_unused, comparing
> to __maybe_unused.
> 
> ---
>  kernel/trace/trace_export.c |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/trace_export.c b/kernel/trace/trace_export.c
> index 934d81f..85309fc 100644
> --- a/kernel/trace/trace_export.c
> +++ b/kernel/trace/trace_export.c
> @@ -48,11 +48,12 @@
>  struct ____ftrace_##name {					\
>  	tstruct							\
>  };								\
> -static void __used ____ftrace_check_##name(void)		\
> +static void __attribute__((unused))				\
> +____ftrace_check_##name(void)					\
>  {								\
>  	struct ____ftrace_##name *__entry = NULL;		\
>  								\
> -	/* force cmpile-time check on F_printk() */		\
> +	/* force compile-time check on F_printk() */		\
>  	printk(print);						\
>  }

Hm, open-coding __attribute__()'s is not good.

These tags are somewhat of a mess:

 #if __GNUC_MINOR__ >= 3
 # define __used                 __attribute__((__used__))
 #else
 # define __used                 __attribute__((__unused__))
 #endif

I've Cc:-ed Linus and Andrew, to solicite feedback on __always_unused. I 
think we should add it.

	Ingo

      reply	other threads:[~2009-10-29  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28  1:44 [PATCH] tracing: Fix to use unused attribute Li Zefan
2009-10-29  7:57 ` Ingo Molnar [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=20091029075735.GC18976@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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