From: Ingo Molnar <mingo@kernel.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, hpa@zytor.com, dwmw@amazon.co.uk,
luto@kernel.org, dave.hansen@linux.intel.com,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] x86/apic: Rudimentary typo fixes
Date: Thu, 25 Mar 2021 15:05:34 +0100 [thread overview]
Message-ID: <20210325140534.GA4167881@gmail.com> (raw)
In-Reply-To: <20210324134149.30445-1-unixbhaskar@gmail.com>
* Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:
> s/preferrable/preferable/
> s/serivced/serviced/
> s/distributon/distribution/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> arch/x86/kernel/apic/apic.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
> index bda4f2a36868..e26ee6e67f47 100644
> --- a/arch/x86/kernel/apic/apic.c
> +++ b/arch/x86/kernel/apic/apic.c
> @@ -619,7 +619,7 @@ static void setup_APIC_timer(void)
>
> if (this_cpu_has(X86_FEATURE_ARAT)) {
> lapic_clockevent.features &= ~CLOCK_EVT_FEAT_C3STOP;
> - /* Make LAPIC timer preferrable over percpu HPET */
> + /* Make LAPIC timer preferable over percpu HPET */
> lapic_clockevent.rating = 150;
> }
>
> @@ -1532,7 +1532,7 @@ static bool apic_check_and_ack(union apic_ir *irr, union apic_ir *isr)
> * Most probably by now the CPU has serviced that pending interrupt and it
> * might not have done the ack_APIC_irq() because it thought, interrupt
> * came from i8259 as ExtInt. LAPIC did not get EOI so it does not clear
> - * the ISR bit and cpu thinks it has already serivced the interrupt. Hence
> + * the ISR bit and cpu thinks it has already serviced the interrupt. Hence
> * a vector might get locked. It was noticed for timer irq (vector
> * 0x31). Issue an extra EOI to clear ISR.
> *
> @@ -1657,7 +1657,7 @@ static void setup_local_APIC(void)
> */
> /*
> * Actually disabling the focus CPU check just makes the hang less
> - * frequent as it makes the interrupt distributon model be more
> + * frequent as it makes the interrupt distribution model be more
> * like LRU than MRU (the short-term load is more even across CPUs).
> */
This and many more comment typos are already fixed in the latest x86
tree, which you can find at:
git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
Thanks,
Ingo
prev parent reply other threads:[~2021-03-25 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 13:41 [PATCH] x86/apic: Rudimentary typo fixes Bhaskar Chowdhury
2021-03-24 17:49 ` Randy Dunlap
2021-03-25 14:05 ` Ingo Molnar [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=20210325140534.GA4167881@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=unixbhaskar@gmail.com \
--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