From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: [Patch 3/4] x86/hpet: Fix ambiguity in broadcast info message.
Date: Mon, 7 Oct 2013 14:26:20 +0100 [thread overview]
Message-ID: <1381152381-19744-4-git-send-email-andrew.cooper3@citrix.com> (raw)
In-Reply-To: <1381152381-19744-1-git-send-email-andrew.cooper3@citrix.com>
"$N will be used for broadcast" is ambiguous between "$N timers" or "timer
$N", particuarly when N is 0.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
CC: Keir Fraser <keir@xen.org>
CC: Jan Beulich <JBeulich@suse.com>
---
xen/arch/x86/hpet.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/hpet.c b/xen/arch/x86/hpet.c
index 99882b1..091e624 100644
--- a/xen/arch/x86/hpet.c
+++ b/xen/arch/x86/hpet.c
@@ -430,7 +430,7 @@ static void __init hpet_fsb_cap_lookup(void)
num_hpets_used++;
}
- printk(XENLOG_INFO "HPET: %u timers (%u will be used for broadcast)\n",
+ printk(XENLOG_INFO "HPET: %u timers (%u timers used for broadcast)\n",
num_chs, num_hpets_used);
}
--
1.7.10.4
next prev parent reply other threads:[~2013-10-07 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 13:26 [Patch 0/4] HPET general fixes Andrew Cooper
2013-10-07 13:26 ` [Patch 1/4] x86/hpet: Basic cleanup Andrew Cooper
2013-10-07 13:26 ` [Patch 2/4] x86/hpet: Sanitise HPET ACPI table and warn about multiple tables Andrew Cooper
2013-10-07 13:45 ` Jan Beulich
2013-10-07 13:55 ` Andrew Cooper
2013-10-07 14:26 ` Jan Beulich
2013-10-07 13:26 ` Andrew Cooper [this message]
2013-10-07 13:48 ` [Patch 3/4] x86/hpet: Fix ambiguity in broadcast info message Jan Beulich
2013-10-07 13:26 ` [Patch 4/4] x86/hpet: Don't clear reserved bits in the General Configuration Register Andrew Cooper
2013-10-07 13:55 ` Jan Beulich
2013-10-07 14:02 ` Andrew Cooper
2013-10-07 14:28 ` Jan Beulich
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=1381152381-19744-4-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).