loss_interval: Fix timeval initialisation
authorIan McDonald <ian.mcdonald@jandi.co.nz>
Mon, 28 May 2007 19:37:45 +0000 (16:37 -0300)
committerDavid S. Miller <davem@sunset.davemloft.net>
Wed, 11 Jul 2007 05:15:06 +0000 (22:15 -0700)
When compiling with EXTRA_CFLAGS=-W noticed that tstamp is not initialised
correctly in dccp_li_calc_first_li.

Signed-off-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Signed-off-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
net/dccp/ccids/ccid3.c

index 2d203ae41aada02e297212b1e99c4239b5dd3fe7..9686a8de2e91ea177c4abab412d383c15f0c75ba 100644 (file)
@@ -829,7 +829,7 @@ static u32 ccid3_hc_rx_calc_first_li(struct sock *sk)
        struct dccp_rx_hist_entry *entry, *next, *tail = NULL;
        u32 x_recv, p;
        suseconds_t rtt, delta;
-       struct timeval tstamp = { 0, };
+       struct timeval tstamp = { 0, };
        int interval = 0;
        int win_count = 0;
        int step = 0;