Neels Hofmeyr df22b00633 osmo_sockaddr_str: API doc: fix 32bit addr mixup of host/network byte order ... Of course both v4 and v6 addresses are kept in network byte order when represented in bytes, but when writing, I somehow must have assumed that inet_pton() returns host byte order. Fix that mixup in the API docs: osmo_sockaddr_str_from_32() and osmo_sockaddr_str_to_32() actually use network byte order. osmo_sockaddr_str_from_32n() and osmo_sockaddr_str_to_32n() actually use host byte order, though reflecting 'n' in their name. sockaddr_str_test: use hexdump instead of %x to show the osmo_sockaddr_str_to_32*() conversions so that the error becomes obvious. (Printing %x reverses the bytes again and made it look correct.) Change-Id: I3cf150cc0cc06dd36039fbde091bc71b01697322		2019-11-23 07:58:47 +00:00
..
sockaddr_str_test.c	osmo_sockaddr_str: API doc: fix 32bit addr mixup of host/network byte order	2019-11-23 07:58:47 +00:00
sockaddr_str_test.ok	osmo_sockaddr_str: API doc: fix 32bit addr mixup of host/network byte order	2019-11-23 07:58:47 +00:00