From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com,
dwmw@amazon.co.uk, maz@kernel.org, peterx@redhat.com,
luto@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch: x86: kernel: apic: Fix spelling theroretical to theoretical in the file vector.c
Date: Wed, 10 Feb 2021 12:42:04 -0800 [thread overview]
Message-ID: <e252b372-c726-68aa-2c35-c64e290e9730@infradead.org> (raw)
In-Reply-To: <20210209135515.3865988-1-unixbhaskar@gmail.com>
On 2/9/21 5:55 AM, Bhaskar Chowdhury wrote:
>
> s/theroretical/theoretical/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> arch/x86/kernel/apic/vector.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/apic/vector.c b/arch/x86/kernel/apic/vector.c
> index 3c9c7492252f..aa9d3cf69580 100644
> --- a/arch/x86/kernel/apic/vector.c
> +++ b/arch/x86/kernel/apic/vector.c
> @@ -1054,7 +1054,7 @@ void irq_force_complete_move(struct irq_desc *desc)
> * of the interrupt on the apic/system bus would be delayed
> * beyond the point where the target cpu disables interrupts
> * in stop machine. I doubt that it can happen, but at least
> - * there is a theroretical chance. Virtualization might be
> + * there is a theoretical chance. Virtualization might be
> * able to expose this, but AFAICT the IOAPIC emulation is not
> * as stupid as the real hardware.
> *
> --
> 2.30.0
>
--
~Randy
prev parent reply other threads:[~2021-02-10 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 13:55 Bhaskar Chowdhury
2021-02-10 20:42 ` Randy Dunlap [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=e252b372-c726-68aa-2c35-c64e290e9730@infradead.org \
--to=rdunlap@infradead.org \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=peterx@redhat.com \
--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
all inboxes | Powered by JetHome®