From: tip-bot for Bjorn Helgaas <bhelgaas@google.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
bhelgaas@google.com, tglx@linutronix.de
Subject: [tip:timers/core] x86/time/rtc: Don' t print extended CMOS year when reading RTC
Date: Thu, 24 Jan 2013 12:16:45 -0800 [thread overview]
Message-ID: <tip-6125bc8b86d9da75ddac77e38f41afbf9f5de3e3@git.kernel.org> (raw)
In-Reply-To: <20130104224146.15189.14874.stgit@bhelgaas.mtv.corp.google.com>
Commit-ID: 6125bc8b86d9da75ddac77e38f41afbf9f5de3e3
Gitweb: http://git.kernel.org/tip/6125bc8b86d9da75ddac77e38f41afbf9f5de3e3
Author: Bjorn Helgaas <bhelgaas@google.com>
AuthorDate: Fri, 4 Jan 2013 15:41:47 -0700
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Thu, 24 Jan 2013 14:56:35 +0100
x86/time/rtc: Don't print extended CMOS year when reading RTC
We shouldn't print the current century every time we read the
RTC.
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/20130104224146.15189.14874.stgit@bhelgaas.mtv.corp.google.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
arch/x86/kernel/rtc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/kernel/rtc.c b/arch/x86/kernel/rtc.c
index 801602b..2e8f3d3 100644
--- a/arch/x86/kernel/rtc.c
+++ b/arch/x86/kernel/rtc.c
@@ -149,7 +149,6 @@ unsigned long mach_get_cmos_time(void)
if (century) {
century = bcd2bin(century);
year += century * 100;
- printk(KERN_INFO "Extended CMOS year: %d\n", century * 100);
} else
year += CMOS_YEARS_OFFS;
prev parent reply other threads:[~2013-01-24 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 22:41 [PATCH] x86: Don't print extended CMOS year when reading RTC Bjorn Helgaas
2013-01-24 20:16 ` tip-bot for Bjorn Helgaas [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-6125bc8b86d9da75ddac77e38f41afbf9f5de3e3@git.kernel.org \
--to=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox