mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	tglx <tglx@linutronix.de>
Subject: Re: [PATCH] scripts/tags.sh: Add magic for trace-events
Date: Thu, 02 Dec 2010 09:13:01 -0500	[thread overview]
Message-ID: <1291299181.12005.3.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1290591835.2072.438.camel@laptop>

On Wed, 2010-11-24 at 10:43 +0100, Peter Zijlstra wrote:
> Make tags find the trace-event definitions
> 
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>

Should we push this patch for 2.6.37? It's small, useful, and does not
impact the kernel whatsoever. But can we call this a bug fix?

-- Steve

> ---
>  scripts/tags.sh |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/scripts/tags.sh b/scripts/tags.sh
> index 8509bb5..bbbe584 100755
> --- a/scripts/tags.sh
> +++ b/scripts/tags.sh
> @@ -125,7 +125,9 @@ exuberant()
>  	-I DEFINE_TRACE,EXPORT_TRACEPOINT_SYMBOL,EXPORT_TRACEPOINT_SYMBOL_GPL \
>  	--extra=+f --c-kinds=-px                                \
>  	--regex-asm='/^ENTRY\(([^)]*)\).*/\1/'                  \
> -	--regex-c='/^SYSCALL_DEFINE[[:digit:]]?\(([^,)]*).*/sys_\1/'
> +	--regex-c='/^SYSCALL_DEFINE[[:digit:]]?\(([^,)]*).*/sys_\1/' \
> +	--regex-c++='/^TRACE_EVENT\(([^,)]*).*/trace_\1/'		\
> +	--regex-c++='/^DEFINE_EVENT\(([^,)]*).*/trace_\1/'
>  
>  	all_kconfigs | xargs $1 -a                              \
>  	--langdef=kconfig --language-force=kconfig              \



  parent reply	other threads:[~2010-12-02 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24  9:43 Peter Zijlstra
2010-11-24 12:37 ` Américo Wang
2010-11-26 15:03 ` [tip:perf/core] " tip-bot for Peter Zijlstra
2010-12-02 14:13 ` Steven Rostedt [this message]
2010-12-16  8:22 ` [tip:perf/urgent] " tip-bot for Peter Zijlstra

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=1291299181.12005.3.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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®