All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: liqin.linux@gmail.com, lennox.wu@gmail.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH] arch/score/kernel/process.c: Remove useless varialbes 'ti' and 'regs'
Date: Sun, 08 Jun 2014 14:58:04 +0800	[thread overview]
Message-ID: <5394097C.9030006@gmail.com> (raw)

They are useless, so remove them, the related warning (with
allmodconfig under score):

    CC      arch/score/kernel/process.o
  arch/score/kernel/process.c: In function 'copy_thread':
  arch/score/kernel/process.c:76:18: warning: unused variable 'regs' [-Wunused-variable]
    struct pt_regs *regs = current_pt_regs();
                    ^
  arch/score/kernel/process.c:74:22: warning: unused variable 'ti' [-Wunused-variable]
    struct thread_info *ti = task_thread_info(p);
                        ^

Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
 arch/score/kernel/process.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/arch/score/kernel/process.c b/arch/score/kernel/process.c
index a1519ad3..50bf1b0 100644
--- a/arch/score/kernel/process.c
+++ b/arch/score/kernel/process.c
@@ -71,9 +71,7 @@ void flush_thread(void) {}
 int copy_thread(unsigned long clone_flags, unsigned long usp,
 		unsigned long arg, struct task_struct *p)
 {
-	struct thread_info *ti = task_thread_info(p);
 	struct pt_regs *childregs = task_pt_regs(p);
-	struct pt_regs *regs = current_pt_regs();
 
 	p->thread.reg0 = (unsigned long) childregs;
 	if (unlikely(p->flags & PF_KTHREAD)) {
-- 
1.7.11.7

             reply	other threads:[~2014-06-08  6:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08  6:58 Chen Gang [this message]
2014-06-12  9:52 ` [PATCH] arch/score/kernel/process.c: Remove useless varialbes 'ti' and 'regs' Liqin Chen

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=5394097C.9030006@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=lennox.wu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liqin.linux@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.