All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: dvhart@linux.intel.com, linux-yocto@yoctoproject.org,
	Rahul.Saxena@intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/8] linux-yocto + kern tools consolidated pull request
Date: Tue, 20 Nov 2012 11:50:09 -0800	[thread overview]
Message-ID: <50ABDEF1.9030607@linux.intel.com> (raw)
In-Reply-To: <cover.1352840087.git.bruce.ashfield@windriver.com>

On 11/14/2012 07:02 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> This is a collection of updates that I've had locally in the last few
> weeks leading up to the 1.3 release, but they were held back to avoid
> any negative impacts on the release.
>
> I've kept all the kernel -stable and configuration updates as distinct
> commits, so it will be possible to separate any issues that crop up
> into manageable chunks. It also shows the different test points that
> I've used while updating the kernels.
>
> For the kernel trees we get the following:
>
>    - the latest 3.2 and 3.4 -stable updates
>    - the latest 3.2 and 3.4 -rt updates
>    - configuration changes that have been collected for BSPs
>
>    ** As far as I'm concerned these are all bugfix/stable changes and
>       can go into danny-next. Others may not agree :)
>
> These have been build tested to the amount that my cycles allow, and
> others have already been used in the meta-intel BSPs. It's worth running
> this through a test build if you are so inclined, just to be sure.
>
> For the tools we get the following updates:
>
>    - A fix for YOCTO #3226 that silences the warning:
>
>         find: warning: -path $oe-path/linux/ will not match anything because it ends with /.
>
>      ** This change should be considering for the danny-next branch as well.
>
>    - A fix to the guilt SRC_URI to point at a valid tgz upstream.
>
>      ** This change should be considering for the danny-next branch as well.
>
>    - kern-tools improvements and fixes that are part of the 1.4 feature work.
>      The kern-tools commit has the details of the changes. They'll be further
>      improved in the upcoming weeks, but they have been in use locally for
>      over a month now, and have been tested by others as well, so they shouldn't
>      cause any problems in master and are invisible to most users.
>
> I've added Ross to the CC for the commits that can be pulled into the 1.3
> maintenance branches.
>
> I've added Rahul since there was some refactoring of the Rangely/dpdk
> configuration that should be checked as well.
>
> Cheers,
>
> Bruce
>
> The following changes since commit 41125ddc8651494ffcf888d3b5efce1ae6d953bb:
>
>    bitbake: print clear message for "bitbake -e ASSUME_PROVIDED" (2012-11-13 14:21:16 +0000)
>
> 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 (8):
>    linux-yocto/3.4: nfsd, pci, fishriver and rangely config changes
>    linux-yocto/3.4: efi/mmc fixes and fri2 updates
>    linux-yocto/3.4: bump kver to v3.4.16
>    linux-yocto/3.4: v3.4.17, v3.4.18, -rt and config changes
>    linux-yocto/3.2: update to v3.2.32 and 3.2.32-rt48
>    kern-tools: kconf_check: fix find warning
>    kern-tools: flexibility and usability enhancements
>    guilt: change upstream tgz location
>
>   meta/recipes-devtools/guilt/guilt-native_0.33.bb     |    4 ++--
>   .../kern-tools/kern-tools-native_git.bb              |    2 +-
>   meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb      |    8 ++++----
>   meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb      |    8 ++++----
>   meta/recipes-kernel/linux/linux-yocto-tiny_3.2.bb    |    6 +++---
>   meta/recipes-kernel/linux/linux-yocto-tiny_3.4.bb    |    7 +++----
>   meta/recipes-kernel/linux/linux-yocto_3.2.bb         |   18 +++++++++---------
>   meta/recipes-kernel/linux/linux-yocto_3.4.bb         |   16 ++++++++--------
>   8 files changed, 34 insertions(+), 35 deletions(-)
>

Merged into OE-Core

Thanks
	Sau!




      parent reply	other threads:[~2012-11-20 20:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 15:02 [PATCH 0/8] linux-yocto + kern tools consolidated pull request Bruce Ashfield
2012-11-14 15:02 ` [PATCH 1/8] linux-yocto/3.4: nfsd, pci, fishriver and rangely config changes Bruce Ashfield
2012-11-14 15:02 ` [PATCH 2/8] linux-yocto/3.4: efi/mmc fixes and fri2 updates Bruce Ashfield
2012-11-14 15:02 ` [PATCH 3/8] linux-yocto/3.4: bump kver to v3.4.16 Bruce Ashfield
2012-11-14 15:03 ` [PATCH 4/8] linux-yocto/3.4: v3.4.17, v3.4.18, -rt and config changes Bruce Ashfield
2012-11-14 15:03 ` [PATCH 5/8] linux-yocto/3.2: update to v3.2.32 and 3.2.32-rt48 Bruce Ashfield
2012-11-14 15:03 ` [PATCH 6/8] kern-tools: kconf_check: fix find warning Bruce Ashfield
2012-11-14 15:03 ` [PATCH 7/8] kern-tools: flexibility and usability enhancements Bruce Ashfield
2012-11-14 16:33   ` Darren Hart
2012-11-14 16:58     ` Bruce Ashfield
2012-11-14 17:09       ` Darren Hart
2012-11-14 17:32         ` Bruce Ashfield
2012-11-14 15:03 ` [PATCH 8/8] guilt: change upstream tgz location Bruce Ashfield
2012-11-20 19:50 ` 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=50ABDEF1.9030607@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Rahul.Saxena@intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=linux-yocto@yoctoproject.org \
    --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.