mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-29 11:11:45 -04:00
Fix common misspellings
Fixes generated by 'codespell' and manually reviewed. Signed-off-by: Lucas De Marchi <[email protected]>
This commit is contained in:
parent
6aba74f279
commit
25985edced
2463 changed files with 4252 additions and 4252 deletions
|
|
@ -5,7 +5,7 @@
|
|||
* domain gets 1024 event channels, but NR_IRQ is not that large, we
|
||||
* must dynamically map irqs<->event channels. The event channels
|
||||
* interface with the rest of the kernel by defining a xen interrupt
|
||||
* chip. When an event is recieved, it is mapped to an irq and sent
|
||||
* chip. When an event is received, it is mapped to an irq and sent
|
||||
* through the normal interrupt processing path.
|
||||
*
|
||||
* There are four kinds of events which can be mapped to an event
|
||||
|
|
@ -416,7 +416,7 @@ static int __must_check xen_allocate_irq_dynamic(void)
|
|||
#ifdef CONFIG_X86_IO_APIC
|
||||
/*
|
||||
* For an HVM guest or domain 0 which see "real" (emulated or
|
||||
* actual repectively) GSIs we allocate dynamic IRQs
|
||||
* actual respectively) GSIs we allocate dynamic IRQs
|
||||
* e.g. those corresponding to event channels or MSIs
|
||||
* etc. from the range above those "real" GSIs to avoid
|
||||
* collisions.
|
||||
|
|
|
|||
Loading…
Reference in a new issue