public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, sandmann@redhat.com
Subject: Re: [PATCH] x86, dumpstack: Fix unused variable warning.
Date: Thu, 25 Nov 2010 07:32:23 +0100	[thread overview]
Message-ID: <20101125073223.1d53b8c6@nowhere> (raw)
In-Reply-To: <AANLkTik9U_Z0WSZ7YjrykER_pBUfPDdgUUmtYx=R74nL@mail.gmail.com>

Le Thu, 25 Nov 2010 11:35:16 +0600,
Rakib Mullick <rakib.mullick@gmail.com> a écrit :

> On Wed, Nov 24, 2010 at 7:19 PM, Frederic Weisbecker
> <fweisbec@gmail.com> wrote:
> > 2010/11/24 Rakib Mullick <rakib.mullick@gmail.com>:
> >
> > Looks like you can even remove that block. bp is not used any more
> > in this function.
> > get_bp() was only loading bp but did not make any use of it.
> 
> Yes, right. Here is the updated one.
> 
>  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>
> ---
> 
> 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,
> 

Queued, thanks!

  reply	other threads:[~2010-11-25  6:32 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 [this message]
2011-01-08 12:06     ` [tip:perf/urgent] " tip-bot for Rakib Mullick

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=20101125073223.1d53b8c6@nowhere \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rakib.mullick@gmail.com \
    --cc=sandmann@redhat.com \
    --cc=x86@kernel.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