>>> On 07.05.18 at 12:11, <davidw...@zhaoxin.com> wrote:
>> -----Original Message-----
>> From: Jan Beulich <jbeul...@suse.com>
>> Sent: Monday, May 7, 2018 4:24 PM
>>
>> >>> On 07.05.18 at 03:37, <davidw...@zhaoxin.com> wrote:
>> > --- a/xen/arch/x86/cpu/intel_cacheinfo.c
>> > +++ b/xen/arch/x86/cpu/intel_cacheinfo.c
>> > @@ -176,7 +176,9 @@ unsigned int init_intel_cacheinfo(struct cpuinfo_x86
>> *c)
>> > * Don't use cpuid2 if cpuid4 is supported. For P4, we use cpuid2 for
>> > * trace cache
>> > */
>> > - if ((num_cache_leaves == 0 || c->x86 == 15) && c->cpuid_level > 1) {
>> > + if ( (num_cache_leaves == 0 || c->x86 == 15) && c->cpuid_level > 1
>> &&
>> > + c->x86_vendor != X86_VENDOR_SHANGHAI )
>>
>> The indentation here is _still_ wrong (and there are stray spaces), but I'll
>> try
>> to remember fixing this up when committing (after 4.11 was branched off),
>> i.e. with that fixed
> To be consistent with context, I indent with two Tabs.
But two tabs aren't consistent with context - a single tab and enough spaces
to properly align with the previous line would be.
> Do I need to submit next version patch to revise it ?
Not strictly - as said, I'll try to remember to correct this while committing.
> Use 4 spaces instead of TAB?
No. You should match the style of surrounding code here, which uses Linux'es
way of indenting.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
