musl/arch/x32/bits/socket.h

struct msghdr {
	void *msg_name;
	socklen_t msg_namelen;
	struct iovec *msg_iov;
	int msg_iovlen, __pad1;
	void *msg_control;
	socklen_t msg_controllen, __pad2;
	int msg_flags;
};

struct cmsghdr {
	socklen_t cmsg_len;
	int __pad1;
	int cmsg_level;
	int cmsg_type;
};
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. 2016-07-03 14:40:11 -04:00			`struct msghdr {`
import vanilla x86_64 code as x32 2014-01-07 22:43:34 +01:00			`void *msg_name;`
			`socklen_t msg_namelen;`
			`struct iovec *msg_iov;`
			`int msg_iovlen, __pad1;`
			`void *msg_control;`
			`socklen_t msg_controllen, __pad2;`
			`int msg_flags;`
			`};`

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. 2016-07-03 14:40:11 -04:00			`struct cmsghdr {`
import vanilla x86_64 code as x32 2014-01-07 22:43:34 +01:00			`socklen_t cmsg_len;`
			`int __pad1;`
			`int cmsg_level;`
			`int cmsg_type;`
			`};`