Search Linux Wireless

Re: [PATCH 20/22] wl1271: Clean up TX security sequence number handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2010-03-09 at 21:45 +0100, ext Kalle Valo wrote:
> Juuso Oikarinen <juuso.oikarinen@xxxxxxxxx> writes:
> 
> > Instead of managing the TX security sequence number as two variables, use
> > one 64 bit variable. This greatly simplifies the handling of the number.
> 
> [...]
> 
> > -	u16 tx_security_seq_16;
> > -	u32 tx_security_seq_32;
> > +	s64 tx_security_seq;
> 
> I'm curious, why s64 and not u64? I'm sure there's a good reason, I
> just wasn't able figure it out.
> 

Hi, good question. I don't remember the reasoning either.

Good news is that we only need the first 48 bits, so it shouldn't matter
so much.

-Juuso

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux