From 75853fa79b3d7824e3f34a2202f6b4f189ad3a02 Mon Sep 17 00:00:00 2001
From: Havard Graff <havard.graff@tandberg.com>
Date: Tue, 13 Oct 2009 17:24:34 +0200
Subject: [PATCH] Make sure that unlinked pads do not cause a return false on
 latency events.

Context: Latency configuration should not be
messed up because of not-linked pads. In general,
one return FALSE on latency distribution causes
the "overall" pipeline latency configuration to
fail. This shows up as noise in logs (warning).

Conflicts:

	gst/gstpad.c
---
 gst/gstpad.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/gst/gstpad.c b/gst/gstpad.c
index d002e15fd2..73981f3320 100644
--- a/gst/gstpad.c
+++ b/gst/gstpad.c
@@ -4430,6 +4430,11 @@ not_linked:
     GST_DEBUG_OBJECT (pad, "Dropping event because pad is not linked");
     GST_OBJECT_FLAG_SET (pad, GST_PAD_FLAG_PENDING_EVENTS);
     gst_event_unref (event);
+
+    /* unlinked pads should not influence latency configuration */
+    if (event_type == GST_EVENT_LATENCY)
+      return GST_FLOW_OK;
+
     return GST_FLOW_NOT_LINKED;
   }
 idle_probe_stopped: