Version: 1
-Previous: 155b557436bc8d4c72364afe2384cd1fb4211bf1
+Previous: bb0faa610b61df595e7e1a0e81851f70bfcb5515
Head: 30ad14a49bfd8e316959952d8fcd3b35ea566e4c
Applied:
rm-build: 55c53dc74f83d371ca0578662774c16c10847dc0
apphang: 39363d3efa43131e2aeb49b42f74b6e446e8b388
cm_send_cb: 30ad14a49bfd8e316959952d8fcd3b35ea566e4c
Unapplied:
- ib_cm_dreq: 31783762cd411bd29a6f46be963978317dc74eb8
epdisc: 4c931f6af5e37a502f7a10b78a902747f9738623
Hidden:
+++ /dev/null
-Bottom: 7c66f1bbc4cd5cc77fb0919d470b377b632c88b7
-Top: 7c66f1bbc4cd5cc77fb0919d470b377b632c88b7
-Author: U-AMR\MSHEFTY <MSHEFTY@mshefty-MOBL2.amr.corp.intel.com>
-Date: 2009-12-14 21:25:59 -0800
-
-ib/cm: avoid DREQ timeout during destruction of CEP
-
-If a user sends DREQs from both sides of a connection, then it's possible
-for the CEP to be in the DREQ received state when the DREP arrives.
-Process the DREP under this condition and cancel the DREQ.
-
-Signed-off-by: Sean Hefty <sean.hefty@intel.com>
-
-
----
-
-