summaryrefslogtreecommitdiff
path: root/include/uapi
diff options
context:
space:
mode:
authorstephen hemminger <stephen@networkplumber.org>2013-08-10 22:22:58 (GMT)
committerDavid S. Miller <davem@davemloft.net>2013-08-13 22:10:22 (GMT)
commitebd8b934e23f45ad3fc8a5a28bc5a96741a6a106 (patch)
treefc30abaada405342996d5f96e343bc499454253d /include/uapi
parent072017b41e49e2a8e8a4e0258837a614bb5daa8d (diff)
downloadlinux-fsl-qoriq-ebd8b934e23f45ad3fc8a5a28bc5a96741a6a106.tar.xz
pptp: fix byte order warnings
Pptp driver has lots of byte order warnings from sparse. This was because the on-the-wire header is in network byte order (obviously) but the definition did not reflect that. Also, the address structure to user space actually put the call id in host order. Rather than break ABI compatibility, just acknowledge the existing design. Signed-off-by: Stephen Hemminger <stephen@networkplumber.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/uapi')
-rw-r--r--include/uapi/linux/if_pppox.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/uapi/linux/if_pppox.h b/include/uapi/linux/if_pppox.h
index e36a4ae..e128769 100644
--- a/include/uapi/linux/if_pppox.h
+++ b/include/uapi/linux/if_pppox.h
@@ -46,7 +46,7 @@ struct pppoe_addr {
* PPTP addressing definition
*/
struct pptp_addr {
- __be16 call_id;
+ __u16 call_id;
struct in_addr sin_addr;
};