···25252626/*2727 * Getting to provable safe in place decompression is hard.2828- * Worst case behaviours need to be analized.2828+ * Worst case behaviours need to be analyzed.2929 * Background information:3030 *3131 * The file layout is:···9494 * Adding 32768 instead of 32767 just makes for round numbers.9595 * Adding the decompressor_size is necessary as it musht live after all9696 * of the data as well. Last I measured the decompressor is about 14K.9797- * 10K of actuall data and 4K of bss.9797+ * 10K of actual data and 4K of bss.9898 *9999 */100100
+2-2
arch/x86/kernel/io_apic_64.c
···1770177017711771/*17721772 *17731773- * IRQ's that are handled by the PIC in the MPS IOAPIC case.17731773+ * IRQs that are handled by the PIC in the MPS IOAPIC case.17741774 * - IRQ2 is the cascade IRQ, and cannot be a io-apic IRQ.17751775 * Linux doesn't really care, as it's not actually used17761776 * for any interrupt handling anyway.···19211921}1922192219231923/*19241924- * MSI mesage composition19241924+ * MSI message composition19251925 */19261926#ifdef CONFIG_PCI_MSI19271927static int msi_compose_msg(struct pci_dev *pdev, unsigned int irq, struct msi_msg *msg)
+2-2
arch/x86/kernel/mce_64.c
···320320#ifdef CONFIG_X86_MCE_INTEL321321/***322322 * mce_log_therm_throt_event - Logs the thermal throttling event to mcelog323323- * @cpu: The CPU on which the event occured.323323+ * @cpu: The CPU on which the event occurred.324324 * @status: Event status information325325 *326326 * This function should be called by the thermal interrupt after the···688688 return 1;689689}690690691691-/* mce=off disables machine check. Note you can reenable it later691691+/* mce=off disables machine check. Note you can re-enable it later692692 using sysfs.693693 mce=TOLERANCELEVEL (number, see above)694694 mce=bootlog Log MCEs from before booting. Disabled by default on AMD.
+1-1
arch/x86/kernel/signal_64.c
···410410411411 signr = get_signal_to_deliver(&info, &ka, regs, NULL);412412 if (signr > 0) {413413- /* Reenable any watchpoints before delivering the413413+ /* Re-enable any watchpoints before delivering the414414 * signal to user space. The processor register will415415 * have been cleared if the watchpoint triggered416416 * inside the kernel.
+1-1
arch/x86/kernel/smpboot_64.c
···350350 /*351351 * We need to hold call_lock, so there is no inconsistency352352 * between the time smp_call_function() determines number of353353- * IPI receipients, and the time when the determination is made353353+ * IPI recipients, and the time when the determination is made354354 * for which cpus receive the IPI in genapic_flat.c. Holding this355355 * lock helps us to not include this cpu in a currently in progress356356 * smp_call_function().
+1-1
arch/x86/kernel/traps_64.c
···201201#define MSG(txt) ops->warning(data, txt)202202203203/*204204- * x86-64 can have upto three kernel stacks: 204204+ * x86-64 can have up to three kernel stacks: 205205 * process stack206206 * interrupt stack207207 * severe exception (double fault, nmi, stack fault, debug, mce) hardware stack
+1-1
arch/x86/kernel/vsyscall_64.c
···5353/*5454 * vsyscall_gtod_data contains data that is :5555 * - readonly from vsyscalls5656- * - writen by timer interrupt or systcl (/proc/sys/kernel/vsyscall64)5656+ * - written by timer interrupt or systcl (/proc/sys/kernel/vsyscall64)5757 * Try to keep this structure as small as possible to avoid cache line ping pongs5858 */5959int __vgetcpu_mode __section_vgetcpu_mode;
+2-2
arch/x86/mm/fault_64.c
···378378 again:379379 /* When running in the kernel we expect faults to occur only to380380 * addresses in user space. All other faults represent errors in the381381- * kernel and should generate an OOPS. Unfortunatly, in the case of an381381+ * kernel and should generate an OOPS. Unfortunately, in the case of an382382 * erroneous fault occurring in a code path which already holds mmap_sem383383 * we will deadlock attempting to validate the fault against the384384 * address space. Luckily the kernel only validly references user···386386 * exceptions table.387387 *388388 * As the vast majority of faults will be valid we will only perform389389- * the source reference check when there is a possibilty of a deadlock.389389+ * the source reference check when there is a possibility of a deadlock.390390 * Attempt to lock the address space, if we cannot we then validate the391391 * source. If this is invalid we can skip the address space check,392392 * thus avoiding the deadlock.
+1-1
arch/x86/mm/srat_64.c
···218218/*219219 * Update nodes_add and decide if to include add are in the zone.220220 * Both SPARSE and RESERVE need nodes_add infomation.221221- * This code supports one contigious hot add area per node.221221+ * This code supports one contiguous hot add area per node.222222 */223223static int reserve_hotadd(int node, unsigned long start, unsigned long end)224224{