From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] kernel: Enable externalsrc on kernels which instantiate kernel.bbclass
Date: Mon, 22 Sep 2014 13:04:47 -0400 [thread overview]
Message-ID: <542056AF.8080009@windriver.com> (raw)
In-Reply-To: <CAMKF1srheZyVe5ATST-ToxZQJkXTTNvoh8j+PzrytSVbjVV9wA@mail.gmail.com>
On 14-09-22 01:03 PM, Khem Raj wrote:
> On Mon, Sep 22, 2014 at 8:27 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
>> But the reports we've been getting have been that externalsrc
>> builds are working for kernels, and linux-yocto without the change
>> in place, so I'm looking to reduce the patch footprint and re-submit.
>
> no, it cant work if folks were trying the usecase I have mentioned.
> The fix is infact for
> non linux-yocto kernels.
I'll send out my updated patch shortly, it should fix both cases.
Bruce
>
next prev parent reply other threads:[~2014-09-22 17:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 10:05 [RFC][PATCH] kernel: Enable externalsrc on kernels which instantiate kernel.bbclass Khem Raj
2014-02-06 13:38 ` Bruce Ashfield
2014-02-06 19:26 ` Bruce Ashfield
2014-02-06 19:36 ` Khem Raj
2014-09-22 15:24 ` [RFC] " Paul Eggleton
2014-09-22 15:27 ` Bruce Ashfield
2014-09-22 17:03 ` Khem Raj
2014-09-22 17:04 ` Bruce Ashfield [this message]
2014-12-03 12:00 ` Paul Eggleton
2014-12-03 12:23 ` Laurentiu Palcu
2014-12-03 13:14 ` Bruce Ashfield
2014-12-03 14:36 ` Paul Eggleton
2014-12-03 16:50 ` Bruce Ashfield
2014-12-04 5:28 ` Bruce Ashfield
2014-12-08 12:10 ` Paul Eggleton
2014-12-08 14:32 ` Bruce Ashfield
2014-12-03 13:12 ` Bruce Ashfield
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=542056AF.8080009@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox