History

modpost: use proper kernel style for autogenerated files

If the kernel build process is creating files automatically, the least it can do is create them in a properly formatted manner. Sure, it's a minor issue, but being consistent is nice.

Greg Kroah-Hartman committed 14 years ago

Commit 3c7ec941 parent eb3d5cc1 file · +4 −4Browse files

Unified · Split

scripts/mod/modpost.c+4−4
@@ -1853,14 +1853,14 @@ static void add_header(struct buffer *b, struct module *mod) · 1852 unmodified lines
18531853 buf_printf(b, "\n");
18541854 buf_printf(b, "struct module __this_module\n");
18551855 buf_printf(b, "__attribute__((section(\".gnu.linkonce.this_module\"))) = {\n");
1856− buf_printf(b, " .name = KBUILD_MODNAME,\n");
1856+ buf_printf(b, "\t.name = KBUILD_MODNAME,\n");
18571857 if (mod->has_init)
1858− buf_printf(b, " .init = init_module,\n");
1858+ buf_printf(b, "\t.init = init_module,\n");
18591859 if (mod->has_cleanup)
18601860 buf_printf(b, "#ifdef CONFIG_MODULE_UNLOAD\n"
1861− " .exit = cleanup_module,\n"
1861+ "\t.exit = cleanup_module,\n"
18621862 "#endif\n");
1863− buf_printf(b, " .arch = MODULE_ARCH_INIT,\n");
1863+ buf_printf(b, "\t.arch = MODULE_ARCH_INIT,\n");
18641864 buf_printf(b, "};\n");
18651865 }
18661866