From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>
Subject: Re: [PATCH] x86/apic: Fix two typos in comments
Date: Thu, 5 Jan 2017 17:57:55 +0800 [thread overview]
Message-ID: <4fe31545-d509-7006-8cd5-7b369a9dfd4d@cn.fujitsu.com> (raw)
In-Reply-To: <20170105081534.GE2098@gmail.com>
Hi, Ingo
At 01/05/2017 04:15 PM, Ingo Molnar wrote:
>
> * Dou Liyang <douly.fnst@cn.fujitsu.com> wrote:
>
>> s/inr_logical_cpuidi/nr_logical_cpuids/
>> s/generic_processor_info()/__generic_processor_info()/
>>
>> Signed-off-by: Dou Liyang <douly.fnst@cn.fujitsu.com>
>> ---
>> arch/x86/kernel/apic/apic.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
>> index 5b7e43e..c32a3ad 100644
>> --- a/arch/x86/kernel/apic/apic.c
>> +++ b/arch/x86/kernel/apic/apic.c
>> @@ -2028,7 +2028,7 @@ void disconnect_bsp_APIC(int virt_wire_setup)
>> /*
>> * The number of allocated logical CPU IDs. Since logical CPU IDs are allocated
>> * contiguously, it equals to current allocated max logical CPU ID plus 1.
>> - * All allocated CPU ID should be in [0, nr_logical_cpuidi), so the maximum of
>> + * All allocated CPU ID should be in [0, nr_logical_cpuids), so the maximum of
>
> There's another typo in that sentence as well, and the wording should be clarified
> as well while at it. Something like this would work for me:
>
>> + * All allocated CPU IDs should be in the [0, nr_logical_cpuids) range,
>> + * so the maximum of
>
Yes, It is. :)
Thanks,
Dou
prev parent reply other threads:[~2017-01-05 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 6:05 Dou Liyang
2017-01-05 8:15 ` Ingo Molnar
2017-01-05 9:57 ` Dou Liyang [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=4fe31545-d509-7006-8cd5-7b369a9dfd4d@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®