diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2024-05-01 16:53:47 +1000 |
---|---|---|
committer | Stefano Brivio <sbrivio@redhat.com> | 2024-05-02 16:13:16 +0200 |
commit | 1095a7b0c9a150cb488ff5bd5fd74c897dd9236e (patch) | |
tree | 6ed45b0641997e440ce18bb7044966937a59ea0b /test | |
parent | 5d37dab012e5d841d9961dec93e1e813d723fdd4 (diff) | |
download | passt-1095a7b0c9a150cb488ff5bd5fd74c897dd9236e.tar passt-1095a7b0c9a150cb488ff5bd5fd74c897dd9236e.tar.gz passt-1095a7b0c9a150cb488ff5bd5fd74c897dd9236e.tar.bz2 passt-1095a7b0c9a150cb488ff5bd5fd74c897dd9236e.tar.lz passt-1095a7b0c9a150cb488ff5bd5fd74c897dd9236e.tar.xz passt-1095a7b0c9a150cb488ff5bd5fd74c897dd9236e.tar.zst passt-1095a7b0c9a150cb488ff5bd5fd74c897dd9236e.zip |
treewide: Remove misleading and redundant endianness notes
In general, it's much less error-prone to have the endianness of values
implied by the type, rather than just noting it in comments. We can't
always easily avoid it, because C, but we can do so when possible. struct
in_addr and in6_addr are always encoded network endian, so noting it
explicitly isn't useful. Remove them.
In some cases we also have endianness notes on uint8_t parameters, which
doesn't make sense: for a single byte endianness is irrelevant. Remove
those too.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions