Re: [PATCH net-next 1/1] net: rmnet_data: Initial implementation

2017-03-08 Thread Subash Abhinov Kasiviswanathan
Inside the kernel you should use "u32", "u16", "u8", etc. for purely internal things, and for datastructures exported to userspace you should use "__u32", "__u16", "__u8". Furthermore, if the members have specific endianness you should properly use the "__le32", "__le16", "__be32", "__be16" etc.

Re: [PATCH net-next 1/1] net: rmnet_data: Initial implementation

2017-03-07 Thread David Miller
From: Subash Abhinov Kasiviswanathan Date: Thu, 23 Feb 2017 20:30:54 -0700 > +struct rmnet_nl_msg_s { > + uint16_t reserved; > + uint16_t message_type; > + uint16_t reserved2:14; > + uint16_t crd:2; Inside the kernel you should use "u32", "u16", "u8",

[PATCH net-next 1/1] net: rmnet_data: Initial implementation

2017-02-23 Thread Subash Abhinov Kasiviswanathan
RmNet Data driver provides a transport agnostic MAP (multiplexing and aggregation protocol) support in embedded and bridge modes. Module provides virtual network devices which can be attached to any IP-mode physical device. This will be used to provide all MAP functionality on future hardware in a

[RFC PATCH net-next 1/1] net: rmnet_data: Initial implementation

2017-02-08 Thread Subash Abhinov Kasiviswanathan
RmNet Data driver provides a transport agnostic MAP (multiplexing and aggregation protocol) support in embedded and bridge modes. Module provides virtual network devices which can be attached to any IP-mode physical device. This will be used to provide all MAP functionality on future hardware in a