From befa5866ee30d09c0c96e88af2eabff5911342ea Mon Sep 17 00:00:00 2001 From: Rich Felker Date: Sun, 3 Jul 2016 14:40:11 -0400 Subject: make brace placement in public header struct definitions consistent placing the opening brace on the same line as the struct keyword/tag is the style I prefer and seems to be the prevailing practice in more recent additions. these changes were generated by the command: find include/ arch/*/bits -name '*.h' \ -exec sed -i '/^struct [^;{]*$/{N;s/\n/ /;}' {} + and subsequently checked by hand to ensure that the regex did not pick up any false positives. --- arch/mips/bits/signal.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'arch/mips/bits/signal.h') diff --git a/arch/mips/bits/signal.h b/arch/mips/bits/signal.h index 889f77e8..db6f22d5 100644 --- a/arch/mips/bits/signal.h +++ b/arch/mips/bits/signal.h @@ -17,8 +17,7 @@ typedef struct { } fp_fregs[32]; } fp_r; } fpregset_t; -struct sigcontext -{ +struct sigcontext { unsigned sc_regmask, sc_status; unsigned long long sc_pc, sc_regs[32], sc_fpregs[32]; unsigned sc_ownedfp, sc_fpc_csr, sc_fpc_eir, sc_used_math, sc_dsp; -- cgit v1.2.1