Openembedded Core Discussions
 help / color / mirror / Atom feed
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/2] linux-yocto: (hopefully) final fixes
Date: Fri, 13 Apr 2012 15:15:39 -0700	[thread overview]
Message-ID: <4F88A58B.9040100@intel.com> (raw)
In-Reply-To: <cover.1334349764.git.bruce.ashfield@windriver.com>

On 04/13/2012 01:55 PM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here are two last commits for linux-yocto. One is a pending
> SRCREV update for the romley. It's included to make sure that the
> meta branch head matches the SRCREVs. Otherwise, we are relying
> on branch renaming for everyone. There's no risk, and this is already
> in use by the BSP layer.
>
> The second commit is a change that I've been working on all week
> with Andrea and his work on extending linux-yocto-tiny. The
> work that was done to support out of tree features was missing
> .cfg and defconfig support. This meant that you could run into
> patching issues.
>
> To fix it, I pulled back changes that I made a few weeks ago
> to allow all types of fragments, features, and defconfigs to
> be supported. The diffstat is largely a movement of code from
> the recipe back to the tools (where it belonged), but the intent
> stays the same.
>
> I've tested this on every use case I could find ..
>
>    - core BSPs
>    - Nitin's x32 use case
>    - Andrea's use case
>    - kernel.org test case
>    - Constructed tests with fragments, nested features, etc.
>
> Andrea has also tested his use case.
>
> These all pass, and the code fixes an intended feature for 1.2 as
> well as fixing the immediate bug in question.
>
> This is for YOCTO 2250.
>
> Cheers,
>
> Bruce
>
> cc: andrea.adami@gmail.com
>
>
> The following changes since commit 023a12b70b1bbbd3625ab5a6df2ae9943a14bea5:
>
>    linux-yocto/meta-yocto: update hardware reference SRCREVs (2012-04-13 16:35:59 -0400)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib zedd/kernel-oe
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe
>
> Bruce Ashfield (2):
>    linux-yocto/3.2: add igb support to romley
>    linux-yocto: allow .cfg, .scc, .patch and defconfigs to be processed
>      in order
>
>   meta/classes/kernel-yocto.bbclass                  |   74 ++------------------
>   .../kern-tools/kern-tools-native_git.bb            |    2 +-
>   meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb    |    2 +-
>   meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb  |    2 +-
>   meta/recipes-kernel/linux/linux-yocto_3.2.bb       |    2 +-
>   5 files changed, 11 insertions(+), 71 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!




      parent reply	other threads:[~2012-04-13 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 20:55 [PATCH 0/2] linux-yocto: (hopefully) final fixes Bruce Ashfield
2012-04-13 20:55 ` [PATCH 1/2] linux-yocto/3.2: add igb support to romley Bruce Ashfield
2012-04-13 20:55 ` [PATCH 2/2] linux-yocto: allow .cfg, .scc, .patch and defconfigs to be processed in order Bruce Ashfield
2012-04-13 22:15 ` 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=4F88A58B.9040100@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox