From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [2011.03-maintenance] Pull request #3
Date: Thu, 17 Mar 2011 11:14:50 -0700 [thread overview]
Message-ID: <4D824F9A.8020903@mentor.com> (raw)
In-Reply-To: <ilt06r$gji$1@dough.gmane.org>
On 03/17/2011 05:52 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Tom,
>
> Please pull the 11 commits from here:
>
> URI: git://dominion.thruhere.net/var/cache/git/openembedded.git
> Branch: 2011.03-maintenance
>
> Koen Kooi (7):
> angstrom 2011.03 blacklist bash-noemu
> task-omap-drivers: task for commonly needed drivers on omap chips
> *beagleboard-validation: collection of tasks iand images to serve
> task-beagleboard*: add changes from latest round of feedback
> linux-omap-psp 2.6.32: add support for xM revision C
> linux-omap-psp 2.6.32: bump PR
> u-boot git: update beagleboard u-boot to 2011.03-RC
>
> chase maupin (4):
> u-boot.inc: allow variable make targets
> dm368-evm: Add configuration for DM368 machine
> matrix-gui: add support for dm386-evm machine
> ti-pru-sw-example: fix building with new toolchain sysroot
>
>
> You can view the branch online at
> http://dominion.thruhere.net/git/cgit.cgi/openembedded/log/?h=2011.03-maintenance
>
> The bash-noemu and u-boot commits both have a one line change compared
> to .dev to account for the differences between angstrom versions. The
> other 9 commits are straight cherry-picks.
Merged, thanks.
> I can pick up the external-toolchain patches from Ben for next weeks
> pull request if you wish.
I've grabbed these with pw-am.sh and updated patchwork. Chase, can you
please update patchwork to reflect that your changes have been applied?
Thanks!
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-17 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 12:52 [2011.03-maintenance] Pull request #3 Koen Kooi
2011-03-17 18:14 ` Tom Rini [this message]
2011-03-17 18:30 ` Maupin, Chase
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=4D824F9A.8020903@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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.