From: Anuj Mittal <anuj.mittal@intel.com>
To: kai.kang@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 2/8] gstreamer1.0-plugins-base: 1.12.4 -> 1.14.0
Date: Wed, 2 May 2018 11:33:07 +0800 [thread overview]
Message-ID: <8265d9ee-a91c-cb5f-33c1-434850f7aad7@intel.com> (raw)
In-Reply-To: <819c96b9c218ece95d000835d8574837450a0e06.1524640773.git.kai.kang@windriver.com>
On 04/25/2018 03:23 PM, kai.kang@windriver.com wrote:
> diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0004-subparse-set-need_segment-after-sink-pad-received-GS.patch b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0004-subparse-set-need_segment-after-sink-pad-received-GS.patch
> index b924e38824..438f4ebbf2 100644
> --- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0004-subparse-set-need_segment-after-sink-pad-received-GS.patch
> +++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base/0004-subparse-set-need_segment-after-sink-pad-received-GS.patch
> @@ -20,7 +20,7 @@ new mode 100755
> index b565e93..7741ccc
> --- a/gst/subparse/gstsubparse.c
> +++ b/gst/subparse/gstsubparse.c
> -@@ -266,22 +266,20 @@ gst_sub_parse_src_event (GstPad * pad, GstObject * parent, GstEvent * event)
> +@@ -270,24 +270,20 @@ gst_sub_parse_src_event (GstPad * pad, GstObject * parent, GstEvent * event)
> goto beach;
> }
>
> @@ -45,13 +45,15 @@ index b565e93..7741ccc
> - GST_DEBUG_OBJECT (self, "segment after seek: %" GST_SEGMENT_FORMAT,
> - &self->segment);
> -
> -- self->need_segment = TRUE;
> +- /* will mark need_segment when receiving segment from upstream,
> +- * after FLUSH and all that has happened,
> +- * rather than racing with chain */
> - } else {
> + if (!ret) {
This probably should be checked if it's still required.
Please consider adding a PACKAGECONFIG to have jpeg enabled too ..
next prev parent reply other threads:[~2018-05-02 3:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 7:23 [PATCH v2 0/8] gstreamer1.0: 1.12.4 -> 1.14.0 kai.kang
2018-04-25 7:23 ` [PATCH v2 1/8] " kai.kang
2018-04-25 7:23 ` [PATCH v2 2/8] gstreamer1.0-plugins-base: " kai.kang
2018-05-02 3:33 ` Anuj Mittal [this message]
2018-05-02 3:40 ` Anuj Mittal
2018-04-25 7:23 ` [PATCH v2 3/8] gstreamer1.0-plugins-bad: " kai.kang
2018-05-02 3:23 ` Anuj Mittal
2018-04-25 7:23 ` [PATCH v2 4/8] gstreamer1.0-plugins-ugly: " kai.kang
2018-04-25 7:23 ` [PATCH v2 5/8] gstreamer1.0-plugins-good: " kai.kang
2018-05-02 3:17 ` Anuj Mittal
2018-05-02 9:26 ` Burton, Ross
2018-04-25 7:23 ` [PATCH v2 6/8] gstreamer1.0-libav: " kai.kang
2018-04-25 7:23 ` [PATCH v2 7/8] gst-validate: " kai.kang
2018-04-25 7:23 ` [PATCH v2 8/8] gstreamer1.0: upgrade other packages to 1.14.0 kai.kang
2018-04-30 12:58 ` [PATCH v2 0/8] gstreamer1.0: 1.12.4 -> 1.14.0 Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8265d9ee-a91c-cb5f-33c1-434850f7aad7@intel.com \
--to=anuj.mittal@intel.com \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox