[TCP]: Update comment about highest_sack validity
authorIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
Fri, 10 Aug 2007 21:31:21 +0000 (14:31 -0700)
committerDavid S. Miller <davem@sunset.davemloft.net>
Wed, 10 Oct 2007 23:48:00 +0000 (16:48 -0700)
commit13dae426318aae073028a4b3bd493104a991e800
tree29c2265378c70c9d771c8127d960455e8d64dc27
parente60402d0a909ca2e6e2fbdf9ed004ef0fae36d33
[TCP]: Update comment about highest_sack validity

This stale info came from the original idea, which proved to be
unnecessarily complex, sacked_out > 0 is easy to do and that when
it's going to be needed anyway (it _can_ be valid also when
sacked_out == 0 but there's not going to be a guarantee about it
for now).

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
include/linux/tcp.h