From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org,
saul.wold@intel.com
Subject: Re: [PATCH 0/9] linux-yocto: consolidated pull request
Date: Fri, 08 Jun 2012 11:58:50 +0100 [thread overview]
Message-ID: <1339153130.30460.2.camel@ted> (raw)
In-Reply-To: <cover.1339098507.git.bruce.ashfield@windriver.com>
On Thu, 2012-06-07 at 15:59 -0400, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here's a 9 patch series that is a collection of work that's been
> brewing for about three weeks.
>
> Highlights include:
>
> - removal of the 2.6.37 recipe, it's time is now gone
> - addition of the 3.4 kernel recipe
> - configuration fixups and audits within that 3.4 kernel
> - kernel *only* support for mips64 mti emulation
> - -stable updates for supported kernels 3.2.18, 3.0.32
> - machine fixes/configurations for the 3.2 and 3.0 kernels
> - kern tool updates, streamlining and fixes
>
> I've built and booted the qemu* machines on 3.4, and have been doing
> this for several weeks now. Built and boot tests have also happened
> on the 3.0 and 3.2 trees as well. Some BSP layers are already using
> these changes.
>
> The tools changes set the stage for some follow on changes that
> I'm nearly done for the next oe-core/yocto release, but they are
> useful by themselves, so I'm getting them out of my queue.
>
> I'll follow up to other lists with updates to recipes and configs
> that reference the modified kernels.
>
> BSP layers can be updated as appropriate, since all these changes
> have been pushed to the various kernel trees.
>
> Cheers,
>
> Bruce
>
> The following changes since commit df8f55a919b3cc602ce1f1c51630c7edf6e36b55:
>
> ltp: Add patch to correct failing build (2012-06-05 23:05:00 +0100)
>
> 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 (9):
> kern-tools: remove unused code, meta branch and directory assumptions
> linux-yocto/3.2: update to v3.2.18
> linux-yocto/3.0: update to v3.0.32
> linux-yocto: remove v2.6.37 recipe
> linux-yocto: add machine aliases for yocto BSPs
> linux-yocto: add 3.4 recipe
> linux-yocto/3.2: fri2 and chiefriver machine updates
> linux-yocto/3.0: add cedartrail kernel features
> kern-tools: anchor KMACHINE test
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-06-08 11:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 19:59 [PATCH 0/9] linux-yocto: consolidated pull request Bruce Ashfield
2012-06-07 19:59 ` [PATCH 1/9] kern-tools: remove unused code, meta branch and directory assumptions Bruce Ashfield
2012-06-07 19:59 ` [PATCH 2/9] linux-yocto/3.2: update to v3.2.18 Bruce Ashfield
2012-06-07 19:59 ` [PATCH 3/9] linux-yocto/3.0: update to v3.0.32 Bruce Ashfield
2012-06-07 19:59 ` [PATCH 4/9] linux-yocto: remove v2.6.37 recipe Bruce Ashfield
2012-06-07 19:59 ` [PATCH 5/9] linux-yocto: add machine aliases for yocto BSPs Bruce Ashfield
2012-06-07 19:59 ` [PATCH 6/9] linux-yocto: add 3.4 recipe Bruce Ashfield
2012-06-07 19:59 ` [PATCH 7/9] linux-yocto/3.2: fri2 and chiefriver machine updates Bruce Ashfield
2012-06-07 19:59 ` [PATCH 8/9] linux-yocto/3.0: add cedartrail kernel features Bruce Ashfield
2012-06-07 19:59 ` [PATCH 9/9] kern-tools: anchor KMACHINE test Bruce Ashfield
2012-06-08 10:58 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-30 12:24 [PATCH 0/9] linux-yocto: consolidated pull request Bruce Ashfield
2016-07-13 1:19 Bruce Ashfield
2017-12-21 15:49 Bruce Ashfield
2019-05-30 12:44 bruce.ashfield
2019-05-31 8:01 ` richard.purdie
2019-05-31 12:53 ` Bruce Ashfield
2019-05-31 13:22 ` richard.purdie
2019-05-31 13:46 ` Bruce Ashfield
2019-05-31 17:07 ` richard.purdie
2019-05-31 21:31 ` Bruce Ashfield
2022-03-05 1:25 bruce.ashfield
2024-03-19 23:01 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=1339153130.30460.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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