Fix: flt.utils.muxer: not always an ERROR to fail to validate
authorPhilippe Proulx <eeppeliteloop@gmail.com>
Tue, 20 Jun 2017 19:50:45 +0000 (15:50 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Thu, 6 Jul 2017 20:15:37 +0000 (16:15 -0400)
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
plugins/utils/muxer/muxer.c

index 8a4ae4e122ba554a1ebe45f5c0997d4651268380..cd9cc3f2f041fba30aed0ce957227c61cc2bccbe 100644 (file)
@@ -1061,11 +1061,7 @@ struct bt_notification_iterator_next_return muxer_notif_iter_do_next(
                next_return.status =
                        validate_muxer_upstream_notif_iters(muxer_notif_iter);
                if (next_return.status != BT_NOTIFICATION_ITERATOR_STATUS_OK) {
-                       BT_LOGE("Cannot validate upstream notification iterator wrappers for muxer's notification iterator: "
-                               "muxer-comp-addr=%p, muxer-notif-iter-addr=%p, "
-                               "status=%s",
-                               muxer_comp, muxer_notif_iter,
-                               bt_notification_iterator_status_string(next_return.status));
+                       /* validate_muxer_upstream_notif_iters() logs details */
                        goto end;
                }
 
This page took 0.024604 seconds and 4 git commands to generate.