From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
David Brownell <dbrownell@users.sourceforge.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] rtc-cmos: Fix boot log message
Date: Mon, 3 Nov 2008 19:52:38 +0100 [thread overview]
Message-ID: <200811031952.39423.elendil@planet.nl> (raw)
In-Reply-To: <200811031942.20360.elendil@planet.nl>
On Monday 03 November 2008, Frans Pop wrote:
> rtc0: alarms up to one month, y3k, 114 bytes nvram, , hpet irqs irqs
Here's a possible patch for this one.
Alternative would be to change the following line at 808:
is_hpet_enabled() ? ", hpet irqs" : "");
to:
is_hpet_enabled() ? "hpet" : "<sensible value>");
Question is what that sensible value would be...
---
From: Frans Pop <elendil@planet.nl>
rtc-cmos: Fix boot log message
-rtc0: alarms up to one month, y3k, 114 bytes nvram, , hpet irqs irqs
+rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Signed-off-by: Frans Pop <elendil@planet.nl>
diff --git a/drivers/rtc/rtc-cmos.c b/drivers/rtc/rtc-cmos.c
index 5549231..6cf8e28 100644
--- a/drivers/rtc/rtc-cmos.c
+++ b/drivers/rtc/rtc-cmos.c
@@ -794,7 +794,7 @@ cmos_do_probe(struct device *dev, struct resource *ports, int rtc_irq)
goto cleanup2;
}
- pr_info("%s: alarms up to one %s%s, %zd bytes nvram, %s irqs\n",
+ pr_info("%s: alarms up to one %s%s, %zd bytes nvram%s\n",
cmos_rtc.rtc->dev.bus_id,
is_valid_irq(rtc_irq)
? (cmos_rtc.mon_alrm
next prev parent reply other threads:[~2008-11-03 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 18:42 Some minor ugliness in changed boot logging Frans Pop
2008-11-03 18:52 ` Frans Pop [this message]
2008-11-03 23:06 ` [PATCH] rtc-cmos: Fix boot log message David Brownell
2008-11-04 16:42 ` Frans Pop
2008-11-07 13:19 ` [PATCH] pcmcia: ensure correct logging in do_io_probe Frans Pop
2008-11-07 13:35 ` [PATCH] pcmcia: minor logging improvement on card detection Frans Pop
2008-11-09 20:43 ` Dominik Brodowski
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=200811031952.39423.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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