From: Sebastian Dröge <sebastian.droege@collabora.co.uk>
Date: Tue, 26 Jun 2012 09:04:23 +0000 (+0200)
Subject: playsink: The default signal handler should be the one that triggers pad blocks and... 
X-Git-Tag: 1.19.3~511^2~6288
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6e4d7e466d91c30ee32df67f59e2e73a6174e7c0;p=platform%2Fupstream%2Fgstreamer.git

playsink: The default signal handler should be the one that triggers pad blocks and reconfiguration

Conflicts:

	gst/playback/gstplaysink.c
---

diff --git a/gst/playback/gstplaysink.c b/gst/playback/gstplaysink.c
index 2947ef7..4689740 100644
--- a/gst/playback/gstplaysink.c
+++ b/gst/playback/gstplaysink.c
@@ -622,7 +622,7 @@ gst_play_sink_class_init (GstPlaySinkClass * klass)
   gstbin_klass->handle_message =
       GST_DEBUG_FUNCPTR (gst_play_sink_handle_message);
 
-  klass->reconfigure = GST_DEBUG_FUNCPTR (gst_play_sink_do_reconfigure);
+  klass->reconfigure = GST_DEBUG_FUNCPTR (gst_play_sink_reconfigure);
   klass->convert_sample = GST_DEBUG_FUNCPTR (gst_play_sink_convert_sample);
 
   _playsink_reset_segment_event_marker_id =