From: tip-bot for Simon Horman <horms@verge.net.au>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, horms@verge.net.au, hpa@zytor.com,
mingo@redhat.com, tglx@linutronix.de
Subject: [tip:timers/urgent] timers: Remove duplicate setting of new_base in __mod_timer()
Date: Thu, 17 Dec 2009 00:36:40 GMT [thread overview]
Message-ID: <tip-cf1e367ee84e02ac349ad0858eb65e8a6a511c8b@git.kernel.org> (raw)
In-Reply-To: <20091217001542.GD25317@verge.net.au>
Commit-ID: cf1e367ee84e02ac349ad0858eb65e8a6a511c8b
Gitweb: http://git.kernel.org/tip/cf1e367ee84e02ac349ad0858eb65e8a6a511c8b
Author: Simon Horman <horms@verge.net.au>
AuthorDate: Thu, 17 Dec 2009 11:15:42 +1100
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 17 Dec 2009 01:30:49 +0100
timers: Remove duplicate setting of new_base in __mod_timer()
new_base is set using per_cpu(tvec_bases, cpu) after selecting the
desired value of cpu immediately below so this line is a unnecessary.
Signed-off-by: Simon Horman <horms@verge.net.au>
LKML-Reference: <20091217001542.GD25317@verge.net.au>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
kernel/timer.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/kernel/timer.c b/kernel/timer.c
index 5db5a8d..15533b7 100644
--- a/kernel/timer.c
+++ b/kernel/timer.c
@@ -656,8 +656,6 @@ __mod_timer(struct timer_list *timer, unsigned long expires,
debug_activate(timer, expires);
- new_base = __get_cpu_var(tvec_bases);
-
cpu = smp_processor_id();
#if defined(CONFIG_NO_HZ) && defined(CONFIG_SMP)
prev parent reply other threads:[~2009-12-17 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 0:15 [PATCH] " Simon Horman
2009-12-17 0:36 ` tip-bot for Simon Horman [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-cf1e367ee84e02ac349ad0858eb65e8a6a511c8b@git.kernel.org \
--to=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@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
all inboxes | Powered by JetHome®