I want to transform some C source files. following Linux kernel coding style. - Does script/Lindent STRICTLY follows all linux kernel coding style rules? - What scripts/templates do you use/suggest for elegant code style with the fact that we are talking about Linux Kernel Coding? The GNU guys suggest indent with the following parameters: -nbad -bap -nbc -bbo -hnl -br -brs -c33 -cd33 -ncdb -ce -ci4 -cli0 -d0 -di1 -nfc1 -i8 -ip0 -l80 -lp -npcs -nprs -npsl -sai -saf -saw -ncs -nsc -sob -nfca -cp33 -ss -ts8 -il1 On the other hand: Linux/script/Lindent contains: -npro -kr -i8 -ts8 -sob -l80 -ss -ncs -cp1 Differences so far: 1) indent with gnu parameters inserts a space on labels eg. err: vs err: 2) indent with gnu parameters inserts 26 spaces #endif /* something like this*/ So probably gnu site is outdated? Also, I have noticed that they both fail theyto leave the empty line of a label empty For example, err: code to err: code What does the coding style suggests in this case? Have you found, other cases such the above?