From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/hpet: force_hpet_broadcast can be __initdata
Date: Fri, 23 Mar 2012 10:24:24 +0000 [thread overview]
Message-ID: <CB91FFD8.3C308%keir@xen.org> (raw)
In-Reply-To: <4F6C4D13020000780007A78D@nat28.tlf.novell.com>
On 23/03/2012 09:14, "Jan Beulich" <JBeulich@suse.com> wrote:
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
> --- 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@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-03-23 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 9:14 [PATCH] x86/hpet: force_hpet_broadcast can be __initdata Jan Beulich
2012-03-23 10:24 ` Keir Fraser [this message]
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=CB91FFD8.3C308%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@suse.com \
--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).