All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "André Draszik" <git@andred.net>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/6] kernel-yocto: streamline patch, configuration and audit phases
Date: Tue, 30 Aug 2016 14:35:42 -0400	[thread overview]
Message-ID: <78886c10-2951-9a57-31dd-0e1e78d19815@windriver.com> (raw)
In-Reply-To: <1472566766.8449.29.camel@andred.net>

On 2016-08-30 10:19 AM, André Draszik wrote:
> On Di, 2016-08-30 at 09:05 -0400, Bruce Ashfield wrote:
>> On 2016-08-30 05:05 AM, André Draszik wrote:
>>>
>>> My kmeta stuff is located directly inside two meta-* layers (i.e. not in
>>> an
>>> extra git repo), where the 2nd layer's kernel recipes .bbappends to the
>>> 1st
>>> one with additional kmeta things.
>>>
>>> This used to work fine, but since this commit it doesn't anymore as only
>>> the
>>> kmeta stuff from the 2nd layer is being copied into workdir.
>>>
>>> Have I been doing something that wasn't guaranteed / supposed to work in
>>> the
>>> first place? Or should that still work? Is it worth fixing or should I
>>> rethink my approach?
>>
>> That was complexity that I had tried to remove, but thinking on it a
>> bit, I think I can restore that without adding much complexity.
>>
>> I'm just finishing work on the 4.8 kernel today, and can look at this
>> tomorrow.
>
> Thank you Bruce!

Can you clarify for me if you are are using SRC_URI items tagged with
'kmeta', i.e. a directory of fragments, or are you just adding .cfg/.scc
items directly to the SRC_URI ?

Bruce

>
>> Do you have any public layers that I can reference to pull together a
>> test case ?
>
> Unfortunately not :-(
>
> But I'm happy to test and report back!
>
>
> Cheers,
> Andre'
>



  reply	other threads:[~2016-08-30 18:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 18:26 [PATCH 0/6] kernel-yocto: consolidated pull request Bruce Ashfield
2016-08-15 18:26 ` [PATCH 1/6] linux-yocto/4.1: netfilter: x_tables: fix stable backport Bruce Ashfield
2016-08-15 18:26 ` [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29 Bruce Ashfield
2016-08-18 15:15   ` Richard Purdie
2016-08-18 15:16     ` Bruce Ashfield
2016-08-18 15:20       ` Richard Purdie
2016-08-19 14:57         ` Bruce Ashfield
2016-08-24 11:25           ` Richard Purdie
2016-08-24 13:14             ` Bruce Ashfield
2016-08-15 18:26 ` [PATCH 3/6] linux-yocto/4.1: config updates Bruce Ashfield
2016-08-15 18:26 ` [PATCH 4/6] linux-yocto/4.4: -rt update patch meta-data to remove () Bruce Ashfield
2016-08-15 18:26 ` [PATCH 5/6] kernel-yocto: streamline patch, configuration and audit phases Bruce Ashfield
2016-08-30  9:05   ` André Draszik
2016-08-30 13:05     ` Bruce Ashfield
2016-08-30 14:19       ` André Draszik
2016-08-30 18:35         ` Bruce Ashfield [this message]
2016-08-31  8:54           ` André Draszik
2016-08-31 20:17             ` Bruce Ashfield
2016-09-01 16:14               ` André Draszik
2016-09-01 20:21                 ` Bruce Ashfield
2016-09-02  3:18                 ` Bruce Ashfield
2016-09-02  4:37                   ` Bruce Ashfield
2016-08-15 18:27 ` [PATCH 6/6] yocto-bsp/yocto-kernel: update to work with the latest kern-tools Bruce Ashfield
2016-08-16 16:00 ` [PATCH 0/6] kernel-yocto: consolidated pull request Burton, Ross
2016-08-16 16:01   ` Bruce Ashfield
2016-08-16 16:10     ` Burton, Ross
2016-08-16 16:11       ` Bruce Ashfield
2016-08-16 16:15         ` Burton, Ross

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=78886c10-2951-9a57-31dd-0e1e78d19815@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=git@andred.net \
    --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.