secure_seq: fix sparse errors
authorEric Dumazet <edumazet@google.com>
Thu, 12 Jan 2017 02:10:37 +0000 (18:10 -0800)
committerDavid S. Miller <davem@davemloft.net>
Thu, 12 Jan 2017 20:57:10 +0000 (15:57 -0500)
commitc1ce1560a1ae1a58505c26bc0e46ce1aee982d54
tree920361b81c67c89bad538dd8f030d89ded1578aa
parenta8ac1a55d0859cf8f53db3275ad4a6480868e80c
secure_seq: fix sparse errors

Fixes following warnings :

net/core/secure_seq.c:125:28: warning: incorrect type in argument 1
(different base types)
net/core/secure_seq.c:125:28:    expected unsigned int const [unsigned]
[usertype] a
net/core/secure_seq.c:125:28:    got restricted __be32 [usertype] saddr
net/core/secure_seq.c:125:35: warning: incorrect type in argument 2
(different base types)
net/core/secure_seq.c:125:35:    expected unsigned int const [unsigned]
[usertype] b
net/core/secure_seq.c:125:35:    got restricted __be32 [usertype] daddr
net/core/secure_seq.c:125:43: warning: cast from restricted __be16
net/core/secure_seq.c:125:61: warning: restricted __be16 degrades to
integer

Fixes: 7cd23e5300c1 ("secure_seq: use SipHash in place of MD5")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Jason A. Donenfeld <Jason@zx2c4.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/core/secure_seq.c