Simply print a warning message. Connection callback doesn't
forward invalid events to consumer so no need to assert.

Signed-off-by: Arlin Davis <[email protected]>
---
 dapl/common/dapl_evd_connection_callb.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/dapl/common/dapl_evd_connection_callb.c 
b/dapl/common/dapl_evd_connection_callb.c
index 3166702..a28d8d6 100644
--- a/dapl/common/dapl_evd_connection_callb.c
+++ b/dapl/common/dapl_evd_connection_callb.c
@@ -181,9 +181,10 @@ dapl_evd_connection_callback(IN dp_ib_cm_handle_t 
ib_cm_handle,
        default:
                {
                        dapl_os_unlock(&ep_ptr->header.lock);
+                       dapl_log(DAPL_DBG_TYPE_WARN,
+                               "dapl_evd_conn_cb() unknown event 0x%x\n",
+                               dat_event_num);
                        evd_ptr = NULL;
-
-                       dapl_os_assert(0);      /* shouldn't happen */
                        break;
                }
        }
-- 
1.7.3



_______________________________________________
ofw mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw

Reply via email to