[PATCH] A few trivial spelling and grammar fixes
A few trivial spelling and grammar mistakes picked up in "arch/x86_64/aperture.c", "arch/x86_64/crash.c" and "arch/x86_64/apic.c". I think all are correct fixes but am ever aware of my fallibility :o) This is my first patch submission so all feedback is appreciated, esp. WRT CCing to Linus, Andi and trivial@kernel.org, is this correct? And which is the most appropriate kernel version to diff against? If any. Should apply cleanly to 2.6.18-rc1 Signed-off-by: Adam Henley <adamazing@gmail.com> Signed-off-by: Andi Kleen <ak@suse.de> - adam
This commit is contained in:
parent
3034d11c93
commit
d5d9ca6d88
|
@ -48,7 +48,7 @@ static u32 __init allocate_aperture(void)
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Aperture has to be naturally aligned. This means an 2GB aperture won't
|
* Aperture has to be naturally aligned. This means an 2GB aperture won't
|
||||||
* have much chances to find a place in the lower 4GB of memory.
|
* have much chance of finding a place in the lower 4GB of memory.
|
||||||
* Unfortunately we cannot move it up because that would make the
|
* Unfortunately we cannot move it up because that would make the
|
||||||
* IOMMU useless.
|
* IOMMU useless.
|
||||||
*/
|
*/
|
||||||
|
|
|
@ -400,7 +400,7 @@ void __cpuinit setup_local_APIC (void)
|
||||||
value |= APIC_SPIV_APIC_ENABLED;
|
value |= APIC_SPIV_APIC_ENABLED;
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Some unknown Intel IO/APIC (or APIC) errata is biting us with
|
* Some unknown Intel IO/APIC (or APIC) errata are biting us with
|
||||||
* certain networking cards. If high frequency interrupts are
|
* certain networking cards. If high frequency interrupts are
|
||||||
* happening on a particular IOAPIC pin, plus the IOAPIC routing
|
* happening on a particular IOAPIC pin, plus the IOAPIC routing
|
||||||
* entry is masked/unmasked at a high rate as well then sooner or
|
* entry is masked/unmasked at a high rate as well then sooner or
|
||||||
|
@ -950,7 +950,7 @@ void smp_local_timer_interrupt(struct pt_regs *regs)
|
||||||
* We take the 'long' return path, and there every subsystem
|
* We take the 'long' return path, and there every subsystem
|
||||||
* grabs the appropriate locks (kernel lock/ irq lock).
|
* grabs the appropriate locks (kernel lock/ irq lock).
|
||||||
*
|
*
|
||||||
* we might want to decouple profiling from the 'long path',
|
* We might want to decouple profiling from the 'long path',
|
||||||
* and do the profiling totally in assembly.
|
* and do the profiling totally in assembly.
|
||||||
*
|
*
|
||||||
* Currently this isn't too much of an issue (performance wise),
|
* Currently this isn't too much of an issue (performance wise),
|
||||||
|
|
|
@ -69,7 +69,7 @@ static void crash_save_this_cpu(struct pt_regs *regs, int cpu)
|
||||||
* for the data I pass, and I need tags
|
* for the data I pass, and I need tags
|
||||||
* on the data to indicate what information I have
|
* on the data to indicate what information I have
|
||||||
* squirrelled away. ELF notes happen to provide
|
* squirrelled away. ELF notes happen to provide
|
||||||
* all of that that no need to invent something new.
|
* all of that, no need to invent something new.
|
||||||
*/
|
*/
|
||||||
|
|
||||||
buf = (u32*)per_cpu_ptr(crash_notes, cpu);
|
buf = (u32*)per_cpu_ptr(crash_notes, cpu);
|
||||||
|
|
Loading…
Reference in New Issue