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. --- include/netinet/tcp.h | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) (limited to 'include/netinet/tcp.h') diff --git a/include/netinet/tcp.h b/include/netinet/tcp.h index d6f41cab..9ea64c45 100644 --- a/include/netinet/tcp.h +++ b/include/netinet/tcp.h @@ -145,8 +145,7 @@ struct tcphdr { #define TCP_CA_Recovery 3 #define TCP_CA_Loss 4 -struct tcp_info -{ +struct tcp_info { uint8_t tcpi_state; uint8_t tcpi_ca_state; uint8_t tcpi_retransmits; @@ -192,8 +191,7 @@ struct tcp_info #define TCP_MD5SIG_MAXKEYLEN 80 -struct tcp_md5sig -{ +struct tcp_md5sig { struct sockaddr_storage tcpm_addr; uint16_t __tcpm_pad1; uint16_t tcpm_keylen; -- cgit v1.2.1