public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Rakib Mullick <rakib.mullick@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	rakib.mullick@gmail.com, a.p.zijlstra@chello.nl,
	fweisbec@gmail.com, sandmann@redhat.com, tglx@linutronix.de,
	mingo@elte.hu
Subject: [tip:perf/urgent] x86, dumpstack: Fix unused variable warning
Date: Sat, 8 Jan 2011 12:06:49 GMT	[thread overview]
Message-ID: <tip-39a6eebda253aa34d659ca9436e3c32ef60473f1@git.kernel.org> (raw)
In-Reply-To: <AANLkTik9U_Z0WSZ7YjrykER_pBUfPDdgUUmtYx=R74nL@mail.gmail.com>

Commit-ID:  39a6eebda253aa34d659ca9436e3c32ef60473f1
Gitweb:     http://git.kernel.org/tip/39a6eebda253aa34d659ca9436e3c32ef60473f1
Author:     Rakib Mullick <rakib.mullick@gmail.com>
AuthorDate: Fri, 7 Jan 2011 16:59:49 +0100
Committer:  Frederic Weisbecker <fweisbec@gmail.com>
CommitDate: Fri, 7 Jan 2011 16:59:49 +0100

x86, dumpstack: Fix unused variable warning

In dump_stack function, bp isn't used anymore, which is introduced by
commit 9c0729dc8062bed96189bd14ac6d4920f3958743. This patch removes bp
completely.

Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Soeren Sandmann <sandmann@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: H. Peter Anvin <hpa@zytor.com>
LKML-Reference: <AANLkTik9U_Z0WSZ7YjrykER_pBUfPDdgUUmtYx=R74nL@mail.gmail.com>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
---
 arch/x86/kernel/dumpstack.c |    6 ------
 1 files changed, 0 insertions(+), 6 deletions(-)

diff --git a/arch/x86/kernel/dumpstack.c b/arch/x86/kernel/dumpstack.c
index 8474c99..d6fb146 100644
--- a/arch/x86/kernel/dumpstack.c
+++ b/arch/x86/kernel/dumpstack.c
@@ -197,14 +197,8 @@ void show_stack(struct task_struct *task, unsigned long *sp)
  */
 void dump_stack(void)
 {
-	unsigned long bp = 0;
 	unsigned long stack;
 
-#ifdef CONFIG_FRAME_POINTER
-	if (!bp)
-		get_bp(bp);
-#endif
-
 	printk("Pid: %d, comm: %.20s %s %s %.*s\n",
 		current->pid, current->comm, print_tainted(),
 		init_utsname()->release,

      parent reply	other threads:[~2011-01-08 12:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24  9:19 [PATCH] x86, dumpstack: Fix unused variable warning Rakib Mullick
2010-11-24  9:57 ` Jesper Juhl
2010-11-24 10:26   ` Rakib Mullick
2010-11-24 13:01     ` Frederic Weisbecker
2010-11-24 13:53       ` Jesper Juhl
2010-11-25  5:36       ` Rakib Mullick
2010-11-25  4:07   ` Valdis.Kletnieks
2010-11-25  6:30     ` Frederic Weisbecker
2010-11-24 13:19 ` Frederic Weisbecker
2010-11-25  5:35   ` Rakib Mullick
2010-11-25  6:32     ` Frederic Weisbecker
2011-01-08 12:06     ` tip-bot for Rakib Mullick [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-39a6eebda253aa34d659ca9436e3c32ef60473f1@git.kernel.org \
    --to=rakib.mullick@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=sandmann@redhat.com \
    --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