mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrew Worsley <amworsley@gmail.com>,
	Phil Carmody <ext-phil.2.carmody@nokia.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <borislav.petkov@amd.com>
Subject: [PATCH] init, calibrate: Drop annoying warning
Date: Tue, 31 May 2011 20:29:01 +0200	[thread overview]
Message-ID: <1306866541-17090-1-git-send-email-bp@amd64.org> (raw)

From: Borislav Petkov <borislav.petkov@amd.com>

Even though the error message is KERN_DEBUG, it appears when booting
every core on setups with 'ignore_loglevel' for people who want to test
latest kernels and scan dmesg for possible issues. Also, it doesn't show
very useful information to the widest audience of kernel boot message
gazers so drop it.

Introduced by d2b463135f84d15808163cd15638b108e323d3e7.

Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
---
 init/calibrate.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/init/calibrate.c b/init/calibrate.c
index cfd7000..2568d22 100644
--- a/init/calibrate.c
+++ b/init/calibrate.c
@@ -93,9 +93,6 @@ static unsigned long __cpuinit calibrate_delay_direct(void)
 		 * If the upper limit and lower limit of the timer_rate is
 		 * >= 12.5% apart, redo calibration.
 		 */
-		printk(KERN_DEBUG "calibrate_delay_direct() timer_rate_max=%lu "
-			    "timer_rate_min=%lu pre_start=%lu pre_end=%lu\n",
-			  timer_rate_max, timer_rate_min, pre_start, pre_end);
 		if (start >= post_end)
 			printk(KERN_NOTICE "calibrate_delay_direct() ignoring "
 					"timer_rate as we had a TSC wrap around"
-- 
1.7.4.rc2


             reply	other threads:[~2011-05-31 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 18:29 Borislav Petkov [this message]
2011-05-31 23:04 ` Andrew Worsley
2011-06-01  6:26   ` Borislav Petkov
2011-06-01 12:52     ` [PATCH v1.1] init, calibrate: Drop annoying printk Borislav Petkov

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=1306866541-17090-1-git-send-email-bp@amd64.org \
    --to=bp@amd64.org \
    --cc=akpm@linux-foundation.org \
    --cc=amworsley@gmail.com \
    --cc=borislav.petkov@amd.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome