public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Lai Jiangshan <laijs@cn.fujitsu.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	guichaz@yahoo.fr, tglx@linutronix.de, laijs@cn.fujitsu.com,
	mingo@elte.hu
Subject: [tip:sched/core] sched, no_hz: Remove unused rq->last_tick_seen field
Date: Sun, 8 Nov 2009 13:07:24 GMT	[thread overview]
Message-ID: <tip-d8c80ce091f6ead6710bc71b58f2c32e5bf855e4@git.kernel.org> (raw)
In-Reply-To: <4AE6A513.6010100@cn.fujitsu.com>

Commit-ID:  d8c80ce091f6ead6710bc71b58f2c32e5bf855e4
Gitweb:     http://git.kernel.org/tip/d8c80ce091f6ead6710bc71b58f2c32e5bf855e4
Author:     Lai Jiangshan <laijs@cn.fujitsu.com>
AuthorDate: Tue, 27 Oct 2009 15:45:23 +0800
Committer:  Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 8 Nov 2009 13:17:47 +0100

sched, no_hz: Remove unused rq->last_tick_seen field

In 15934a37324f32e0fda633dc7984a671ea81cd75,
field last_tick_seen is added to struct rq.
But it is unused now.

Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Guillaume Chazarain <guichaz@yahoo.fr>
LKML-Reference: <4AE6A513.6010100@cn.fujitsu.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 kernel/sched.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/kernel/sched.c b/kernel/sched.c
index f849212..23e3535 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -534,7 +534,6 @@ struct rq {
 	#define CPU_LOAD_IDX_MAX 5
 	unsigned long cpu_load[CPU_LOAD_IDX_MAX];
 #ifdef CONFIG_NO_HZ
-	unsigned long last_tick_seen;
 	unsigned char in_nohz_recently;
 #endif
 	/* capture load from *all* tasks on this cpu: */

      reply	other threads:[~2009-11-08 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27  7:45 [PATCH] no_hz: remove unused field Lai Jiangshan
2009-11-08 13:07 ` tip-bot for Lai Jiangshan [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-d8c80ce091f6ead6710bc71b58f2c32e5bf855e4@git.kernel.org \
    --to=laijs@cn.fujitsu.com \
    --cc=guichaz@yahoo.fr \
    --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=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