Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/7] linux-yocto/3.8: allow kernel feature _appends to be overriden
Date: Tue, 26 Mar 2013 15:50:58 -0400	[thread overview]
Message-ID: <5151FC22.2080002@windriver.com> (raw)
In-Reply-To: <5151C4BC.4050108@linux.intel.com>

On 13-03-26 11:54 AM, Darren Hart wrote:
>
>
> On 03/26/2013 08:49 AM, Bruce Ashfield wrote:
>> On 13-03-26 11:48 AM, Darren Hart wrote:
>>> On 03/26/2013 07:46 AM, Bruce Ashfield wrote:
>>>> It was pointed out that the current way the KERNEL_FEATURES variable
>>>> is appended in the base linux-yocto recipe doesn't allow the appended
>>>> features to be prevented in a layer without using python code and
>>>> a recipe finalize hook.
>>>>
>>>> To allow easier overriding of 'extra' or 'optional' features that are
>>>> defined in the linux-yocto recipe, we create a KERNEL_EXTRA_FEATURES
>>>> variable. This variable can be set in a layer to define extra features
>>>> or cleared to prevent the recipe's extra features from being appended
>>>> to the core functionality.
>>>
>>> You know what I'm going to say right? Docume.... right, good.
>>>
>>> Bruce, are you keeping a list of things that have changed and need
>>> documentation in the kernel-dev manual? Could you share it?
>>
>> I do have a list, I'll put it in bugzilla.
>
> Thank you sir!

I'm overloading bug 3423 with the list of documentation updates that I'll
send out for 1.4 .. it has now been updated.

Cheers,

Bruce

>




  reply	other threads:[~2013-03-26 20:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 14:46 [PATCH 0/7] linux-yocto: M6 -stable updates and changes Bruce Ashfield
2013-03-26 14:46 ` [PATCH 1/7] linux-yocto/3.8: allow kernel feature _appends to be overriden Bruce Ashfield
2013-03-26 15:48   ` Darren Hart
2013-03-26 15:49     ` Bruce Ashfield
2013-03-26 15:54       ` Darren Hart
2013-03-26 19:50         ` Bruce Ashfield [this message]
2013-03-26 14:46 ` [PATCH 2/7] linux/yocto-3.4: update to v3.8.4 Bruce Ashfield
2013-03-26 14:46 ` [PATCH 3/7] linux-yocto/3.8: introduce v3.8.4-rt1 Bruce Ashfield
2013-03-28 15:40   ` Tom Zanussi
2013-03-28 15:48     ` Bruce Ashfield
2013-03-28 15:51       ` Tom Zanussi
2013-03-26 14:46 ` [PATCH 4/7] kern-tools: initialization and meta branch fixes Bruce Ashfield
2013-03-26 14:46 ` [PATCH 5/7] linux-yocto/3.4: import v3.4.36 -stable fixes Bruce Ashfield
2013-03-26 14:46 ` [PATCH 6/7] linux-yocto/3.8: fix perf host contamination Bruce Ashfield
2013-03-26 14:46 ` [PATCH 7/7] linux-yocto/3.8: qemuarm boot fix 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=5151FC22.2080002@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox