On 04/15/2015 03:45 PM, Joe Hershberger wrote:
> Hi Michal,
>
> On Wed, Apr 15, 2015 at 5:50 AM, Michal Simek
> wrote:
>>
>> From: Siva Durga Prasad Paladugu
>>
>> Based on rfc951 transaction ID has 4 bytes which is not the case when
>> ulong type is used on ARM64.
>> Use u32 type which is well
Hi Michal,
On Wed, Apr 15, 2015 at 5:50 AM, Michal Simek
wrote:
>
> From: Siva Durga Prasad Paladugu
>
> Based on rfc951 transaction ID has 4 bytes which is not the case when
> ulong type is used on ARM64.
> Use u32 type which is well defined for all archs.
>
> BOOTP_VENDOR_MAGIC is also 4 bytes
On Wed, Apr 15, 2015 at 12:50:59PM +0200, Michal Simek wrote:
> From: Siva Durga Prasad Paladugu
>
> Based on rfc951 transaction ID has 4 bytes which is not the case when
> ulong type is used on ARM64.
> Use u32 type which is well defined for all archs.
>
> BOOTP_VENDOR_MAGIC is also 4 bytes.
>
From: Siva Durga Prasad Paladugu
Based on rfc951 transaction ID has 4 bytes which is not the case when
ulong type is used on ARM64.
Use u32 type which is well defined for all archs.
BOOTP_VENDOR_MAGIC is also 4 bytes.
Based on RFC1048 Time Offset (code 2) is also 4bytes long
and IP Address Leas
4 matches
Mail list logo