From: akpm@linux-foundation.org
To: lizf@cn.fujitsu.com, johnstul@us.ibm.com, mingo@elte.hu,
tglx@linutronix.de, mm-commits@vger.kernel.org
Subject: - clocksource-remove-redundant-code.patch removed from -mm tree
Date: Fri, 08 Feb 2008 12:14:42 -0800 [thread overview]
Message-ID: <200802082014.m18KENFc010414@imap1.linux-foundation.org> (raw)
The patch titled
clocksource: remove redundant code
has been removed from the -mm tree. Its filename was
clocksource-remove-redundant-code.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: clocksource: remove redundant code
From: Li Zefan <lizf@cn.fujitsu.com>
Flag CLOCK_SOURCE_WATCHDOG is cleared twice. Note clocksource_change_rating()
won't do anyting with the cs flag.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: john stultz <johnstul@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/time/clocksource.c | 1 -
1 file changed, 1 deletion(-)
diff -puN kernel/time/clocksource.c~clocksource-remove-redundant-code kernel/time/clocksource.c
--- a/kernel/time/clocksource.c~clocksource-remove-redundant-code
+++ a/kernel/time/clocksource.c
@@ -91,7 +91,6 @@ static void clocksource_ratewd(struct cl
cs->name, delta);
cs->flags &= ~(CLOCK_SOURCE_VALID_FOR_HRES | CLOCK_SOURCE_WATCHDOG);
clocksource_change_rating(cs, 0);
- cs->flags &= ~CLOCK_SOURCE_WATCHDOG;
list_del(&cs->wd_list);
}
_
Patches currently in -mm which might be from lizf@cn.fujitsu.com are
origin.patch
reply other threads:[~2008-02-08 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200802082014.m18KENFc010414@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--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 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.