diff options
| author | Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> | 2007-12-01 17:47:57 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2008-01-28 17:55:40 -0500 |
| commit | 407ef1de03e87225d75a9bed271f35ea6880f5f1 (patch) | |
| tree | 5003ff9db585997fceda75340f4631c311b0fe51 /include/crypto | |
| parent | bce392f3b02755a8c615d4ced3d3b9cb1d9e3648 (diff) | |
[TCP]: Remove superflucious FLAG_DATA_SACKED
To get there, highest_sack must have advanced. When it advances,
a new skb is SACKed, which already sets that FLAG. Besides, the
original purpose of it has puzzled me, never understood why
LOST bit setting of retransmitted skb is marked with
FLAG_DATA_SACKED.
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/crypto')
0 files changed, 0 insertions, 0 deletions