From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/2] x86/cpu: Introduce cpu_dev.c_early_init()
Date: Fri, 27 Nov 2015 09:59:11 +0000 [thread overview]
Message-ID: <5658296F.3070505@citrix.com> (raw)
In-Reply-To: <5658214E02000078000B98CE@prv-mh.provo.novell.com>
On 27/11/15 08:24, Jan Beulich wrote:
>>>> On 26.11.15 at 17:58, <andrew.cooper3@citrix.com> wrote:
>> The name is chosen to be consistent with Linux. Doing this allows
>> early_intel_workaround() to be removed from common code.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> with one adjustment suggestion (which I'll do on commit unless you
> object):
Absolutely fine.
>
>> --- a/xen/arch/x86/cpu/intel.c
>> +++ b/xen/arch/x86/cpu/intel.c
>> @@ -156,10 +156,8 @@ static void __devinit set_cpuidmask(const struct cpuinfo_x86 *c)
>> }
>> }
>>
>> -void __devinit early_intel_workaround(struct cpuinfo_x86 *c)
>> +static void __devinit early_init_intel(struct cpuinfo_x86 *c)
> The __devinit should be dropped here considering that we mean
> to drop them gradually anyway.
I shall dust off my series which drops them all.
~Andrew
prev parent reply other threads:[~2015-11-27 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 16:58 [PATCH 1/2] x86/cpu: Introduce cpu_dev.c_early_init() Andrew Cooper
2015-11-26 16:59 ` [PATCH 2/2] x86/cpu: Move set_cpumask() calls into c_early_init() Andrew Cooper
2015-11-27 8:28 ` Jan Beulich
2015-11-27 10:57 ` Andrew Cooper
2015-11-27 11:11 ` Jan Beulich
2015-11-27 12:03 ` Andrew Cooper
2015-11-27 8:24 ` [PATCH 1/2] x86/cpu: Introduce cpu_dev.c_early_init() Jan Beulich
2015-11-27 9:59 ` Andrew Cooper [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=5658296F.3070505@citrix.com \
--to=andrew.cooper3@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.