All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Specify extra paths
Date: Thu, 18 Aug 2016 09:50:49 -0700	[thread overview]
Message-ID: <2670E9D0-AF83-4FE0-A846-ADC4384298BC@gmail.com> (raw)
In-Reply-To: <CAJTo0LYU11Jvqyv+D=qgreP8mGYchLQF1JJbosNmtBo6ONtSeQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 866 bytes --]


> On Aug 18, 2016, at 9:47 AM, Burton, Ross <ross.burton@intel.com> wrote:
> 
> 
> On 18 August 2016 at 17:41, Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>> wrote:
> Some layers have gstreamer plugin recipes which include
> the .inc files from OE-Core but they do not get to find
> the patch that is being forced by the .inc file and
> ends up with errors like
> 
> Bad commit message as you don't specify the module.
> 
> But should this SRC_URI_append be in the common plugins.inc anyway?  Are there out-of-tree modules that don't use gst-common and so the patch won't apply?

yes there are see
https://github.com/ndechesne/meta-qcom/blob/master/recipes-multimedia/gstreamer/gstreamer1.0-plugins-v4l2.bb <https://github.com/ndechesne/meta-qcom/blob/master/recipes-multimedia/gstreamer/gstreamer1.0-plugins-v4l2.bb>



> 
> Ross


[-- Attachment #1.2: Type: text/html, Size: 2045 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

  reply	other threads:[~2016-08-18 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18 16:41 [PATCH] Specify extra paths Khem Raj
2016-08-18 16:47 ` Burton, Ross
2016-08-18 16:50   ` Khem Raj [this message]
2016-08-18 17:08 ` Martin Jansa
2016-08-18 17:34   ` Khem Raj

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=2670E9D0-AF83-4FE0-A846-ADC4384298BC@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.