5fd8dd203a
Most, but not all our C code follows the Linux kernel code style (as documented in Documentation/process/coding-style.rst). Adjust the few places doing differently: - Braces: ..but the preferred way, as shown to us by the prophets Kernighan and Ritchie, is to put the opening brace last on the line - Spaces after keywords: Use a space after (most) keywords Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
---|---|---|
.. | ||
apply-patches.sh | ||
br2-external | ||
brpkgutil.py | ||
check-bin-arch | ||
check-host-rpath | ||
check-kernel-headers.sh | ||
check-merged-usr.sh | ||
eclipse-register-toolchain | ||
expunge-gconv-modules | ||
fix-configure-powerpc64.sh | ||
fix-rpath | ||
generate-gitlab-ci-yml | ||
genimage.sh | ||
graph-build-time | ||
graph-depends | ||
hardlink-or-copy | ||
mkmakefile | ||
mkusers | ||
pkg-stats | ||
pycompile.py | ||
setlocalversion | ||
size-stats |