From: Saul Wold <saul.wold@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org
Subject: Re: [PATCH 0/1] linux-yocto: BSP updates
Date: Thu, 03 Feb 2011 11:37:13 -0800 [thread overview]
Message-ID: <4D4B03E9.2000000@intel.com> (raw)
In-Reply-To: <cover.1296666481.git.bruce.ashfield@windriver.com>
On 02/02/2011 09:11 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here's the update for the sugarbay and beagleboard BSPs. To make the sugarbay
> inhert common-pc-64 generic config/changes/fixes it has been
> branched in the kernel as yocto/standard/common-pc-64/sugarbar, as
> a result, we'll bump the common-pc-64 to be yocto/standard/common-pc-64/base.
>
> I've built the common-pc-64, sugarbay and beagleboard here. Branch
> renames and creations have been pushed to the repos.
>
> This commit also stages lttng for a single board qemux86, but more
> will follow by the end of day.
>
> cc'ing Tom and Darren, since they both have changes pending on this
> making it into the tree.
>
> cc: Darren Hart<dvhart@linux.intel.com>
> cc: Tom Zanussi<tom.zanussi@intel.com>
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: zedd/bsp
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/bsp
>
> Thanks,
> Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (1):
> linux-yocto: BSP updates
>
> .../conf/distro/include/poky-default-revisions.inc | 24 ++++++++++----------
> meta/recipes-kernel/linux/linux-yocto_git.bb | 2 +-
> 2 files changed, 13 insertions(+), 13 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Merged into Master
Thanks
Sau!
prev parent reply other threads:[~2011-02-03 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 17:11 [PATCH 0/1] linux-yocto: BSP updates Bruce Ashfield
2011-02-02 17:11 ` [PATCH 1/1] " Bruce Ashfield
2011-02-03 19:37 ` 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=4D4B03E9.2000000@intel.com \
--to=saul.wold@intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=yocto@yoctoproject.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