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

Re: [Xen-devel] [PATCH] x86/hpet: force_hpet_broadcast can be __initdata


  • To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Fri, 23 Mar 2012 10:24:24 +0000
  • Delivery-date: Fri, 23 Mar 2012 10:25:10 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac0I3x4jSYfaOlcXoUaAPa2D7vDy9A==
  • Thread-topic: [Xen-devel] [PATCH] x86/hpet: force_hpet_broadcast can be __initdata

On 23/03/2012 09:14, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Acked-by: Keir Fraser <keir@xxxxxxx>

> --- a/xen/arch/x86/hpet.c
> +++ b/xen/arch/x86/hpet.c
> @@ -57,7 +57,7 @@ unsigned long __read_mostly hpet_address
>   * if RTC interrupts are enabled. Enable this option if want to always enable
>   * legacy hpet broadcast for deep C state
>   */
> -static bool_t __read_mostly force_hpet_broadcast;
> +static bool_t __initdata force_hpet_broadcast;
>  boolean_param("hpetbroadcast", force_hpet_broadcast);
>  
>  /*
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



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


 


Rackspace

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