From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] linux-yocto: restore WORKDIR as a patch source directory
Date: Thu, 19 Jan 2012 12:00:42 -0800 [thread overview]
Message-ID: <4F18766A.9050504@intel.com> (raw)
In-Reply-To: <cover.1326906635.git.bruce.ashfield@windriver.com>
On 01/18/2012 09:13 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> As was pointed out on IRC this morning, config fragments and other
> config tweaks that were added to the SRC_URI weren't being processed
> by the config phase of the linux-yocto build.
>
> When I switched to using src_patches, I dropped WORKDIR as a
> directory that would be scanned for patches and configs. This patch
> restores that functionality by putting WORKDIR back into the
> path that will be searched.
>
> Cheers,
>
> Bruce
>
> The following changes since commit 5724ee9c3a99519fea96446638910b727b89898d:
> Mark Hatle (1):
> package_rpm.bbclass: Add support for filenames with spaces
>
> are available in the git repository at:
>
> git://git.pokylinux.org/poky-contrib zedd/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (1):
> linux-yocto: restore WORKDIR as a patch source directory
>
> meta/classes/kernel-yocto.bbclass | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-01-19 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 17:13 [PATCH 0/1] linux-yocto: restore WORKDIR as a patch source directory Bruce Ashfield
2012-01-18 17:13 ` [PATCH 1/1] " Bruce Ashfield
2012-01-19 20:00 ` Saul Wold [this message]
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=4F18766A.9050504@intel.com \
--to=saul.wold@intel.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 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.