[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC 3/8] x86/hpet: Fix ambiguity in broadcast info message.

To: Jan Beulich <JBeulich@xxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Tue, 5 Nov 2013 13:36:02 +0000
Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 05 Nov 2013 13:36:23 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 05/11/13 13:34, Jan Beulich wrote:
> 
> How about "HPET: %u timers usable for broadcast (%u total)"?

This works for me.

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [RFC 0/8] Improvements to HPET interupts
  - From: Andrew Cooper
- [Xen-devel] [RFC 3/8] x86/hpet: Fix ambiguity in broadcast info message.
  - From: Andrew Cooper
- Re: [Xen-devel] [RFC 3/8] x86/hpet: Fix ambiguity in broadcast info message.
  - From: Jan Beulich
- Re: [Xen-devel] [RFC 3/8] x86/hpet: Fix ambiguity in broadcast info message.
  - From: David Vrabel
- Re: [Xen-devel] [RFC 3/8] x86/hpet: Fix ambiguity in broadcast info message.
  - From: Jan Beulich

Prev by Date: Re: [Xen-devel] [RFC 3/8] x86/hpet: Fix ambiguity in broadcast info message.
Next by Date: Re: [Xen-devel] [PATCH v2 1/1] .config: Allow all URL(s) to be specified in .config
Previous by thread: Re: [Xen-devel] [RFC 3/8] x86/hpet: Fix ambiguity in broadcast info message.
Next by thread: [Xen-devel] [RFC 5/8] x86/msi: Refactor msi_compose_message() to not requrie an irq_desc
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.