public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Richard Weinberger <richard@nod.at>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
	rostedt@goodmis.org, richard@nod.at, tglx@linutronix.de
Subject: [tip:perf/core] tracing: Remove kernel_lock annotations
Date: Mon, 21 May 2012 02:46:33 -0700	[thread overview]
Message-ID: <tip-895b67fd5830ce18a6f1375a7c062fcf84b4b874@git.kernel.org> (raw)
In-Reply-To: <1320654202-4433-1-git-send-email-richard@nod.at>

Commit-ID:  895b67fd5830ce18a6f1375a7c062fcf84b4b874
Gitweb:     http://git.kernel.org/tip/895b67fd5830ce18a6f1375a7c062fcf84b4b874
Author:     Richard Weinberger <richard@nod.at>
AuthorDate: Mon, 7 Nov 2011 09:23:22 +0100
Committer:  Steven Rostedt <rostedt@goodmis.org>
CommitDate: Sat, 19 May 2012 08:28:51 -0400

tracing: Remove kernel_lock annotations

The BKL is gone, these annotations are useless.

Link: http://lkml.kernel.org/r/1320654202-4433-1-git-send-email-richard@nod.at

Signed-off-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
 kernel/trace/trace.c |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index a44d4c6..b9a507c 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -763,8 +763,6 @@ update_max_tr_single(struct trace_array *tr, struct task_struct *tsk, int cpu)
  * Register a new plugin tracer.
  */
 int register_tracer(struct tracer *type)
-__releases(kernel_lock)
-__acquires(kernel_lock)
 {
 	struct tracer *t;
 	int ret = 0;

      reply	other threads:[~2012-05-21  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  8:23 [PATCH 2/3] trace: Remove kernel_lock annotations Richard Weinberger
2012-05-21  9:46 ` tip-bot for Richard Weinberger [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=tip-895b67fd5830ce18a6f1375a7c062fcf84b4b874@git.kernel.org \
    --to=richard@nod.at \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.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