On Fri, Mar 6, 2015 at 5:33 AM, Borislav Petkov <bp@xxxxxxx> wrote: > Please use checkpatch before submitting patches: > > WARNING: please, no spaces at the start of a line > #71: FILE: arch/x86/kernel/setup.c:433: > + unsigned char *data;$ > > WARNING: please, no spaces at the start of a line > #72: FILE: arch/x86/kernel/setup.c:434: > + unsigned long offset = sizeof(struct setup_data);$ > > WARNING: please, no spaces at the start of a line > #74: FILE: arch/x86/kernel/setup.c:436: > + data = early_memremap(pa_data, offset + 1);$ > > WARNING: please, no spaces at the start of a line > #75: FILE: arch/x86/kernel/setup.c:437: > + if (!data) {$ > > ERROR: code indent should use tabs where possible > #76: FILE: arch/x86/kernel/setup.c:438: > + kaslr_enabled = true;$ > > WARNING: please, no spaces at the start of a line > #76: FILE: arch/x86/kernel/setup.c:438: > + kaslr_enabled = true;$ > > ERROR: code indent should use tabs where possible > #77: FILE: arch/x86/kernel/setup.c:439: > + return;$ > > WARNING: please, no spaces at the start of a line > #77: FILE: arch/x86/kernel/setup.c:439: > + return;$ > > WARNING: please, no spaces at the start of a line > #78: FILE: arch/x86/kernel/setup.c:440: > + }$ > > WARNING: please, no spaces at the start of a line > #80: FILE: arch/x86/kernel/setup.c:442: > + kaslr_enabled = *(data + offset);$ > > WARNING: please, no spaces at the start of a line > #81: FILE: arch/x86/kernel/setup.c:443: > + early_memunmap(data, offset + 1);$ > > total: 2 errors, 9 warnings, 19 lines checked > > NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or > scripts/cleanfile > > Your patch has style problems, please review. > > If any of these errors are false positives, please report > them to the maintainer, see CHECKPATCH in MAINTAINERS. > That is "copy and paste" instead of attachment for easy review. but gmail web client convert tab to spaces. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html