| To: | becker@xxxxxxxxx |
|---|---|
| Subject: | Re: tx_timeout and timer serialisation |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Sat, 20 May 2000 00:31:21 -0700 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.10.10005200311540.825-100000@vaio.greennet> (message from Donald Becker on Sat, 20 May 2000 03:25:53 -0400 (EDT)) |
| References: | <Pine.LNX.4.10.10005200311540.825-100000@vaio.greennet> |
| Sender: | owner-netdev@xxxxxxxxxxx |
Date: Sat, 20 May 2000 03:25:53 -0400 (EDT) From: Donald Becker <becker@xxxxxxxxx> Backwards compatibility is pointlessly made more painful by such a change. It's almost as bad as changing a interface function's argument count without changing the name, or changing the element order of a structure that is commonly statically initialized. del_timer deschedules a timer, no more, no less. Later, David S. Miller davem@xxxxxxxxxx |
| Previous by Date: | Re: tx_timeout and timer serialisation, Donald Becker |
|---|---|
| Next by Date: | Re: [PATCH]: Cruft fixes, Jeff Garzik |
| Previous by Thread: | Re: tx_timeout and timer serialisation, Donald Becker |
| Next by Thread: | Re: tx_timeout and timer serialisation, Donald Becker |
| Indexes: | [Date] [Thread] [Top] [All Lists] |