From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][2011.003-maintenance] ti-pru-sw-example: fix building with new toolchain sysroot
Date: Thu, 17 Mar 2011 08:44:56 +0100 [thread overview]
Message-ID: <ilse5o$fd4$1@dough.gmane.org> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F080340AC3EC2@dlee06.ent.ti.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 16-03-11 20:02, Maupin, Chase wrote:
>> From: openembedded-devel-bounces@lists.openembedded.org
>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
>> Koen Kooi
>> Sent: Wednesday, March 16, 2011 1:22 PM
>> To: openembedded-devel@lists.openembedded.org
>> Subject: Re: [oe] [PATCH][2011.003-maintenance] ti-pru-sw-example: fix
>> building with new toolchain sysroot
>>
> On 16-03-11 18:22, Chase Maupin wrote:
>>>> * Patch taken from Arago overlay where it was added by
>>>> Denys Dmytriyenko
>>>> * PR incremented by two to align recipe PR values between Arago
>>>> and OE.
>>>>
>>>> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
>
> NAK, this hasn't been thru .dev yet.
>
>> Just submitted all 4 of my patches for .dev. Thanks.
I've staged them here:
http://dominion.thruhere.net/git/cgit.cgi/openembedded/log/?h=2011.03-maintenance
(subject to rebasing).
Do you want to would for the pull request to go out tomorrow, or do you
want Tom to pick up your patches seperately?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNgbv3MkyGM64RGpERAhAuAJ4iE8FFf/ZNqHJF06GSeOEhum9y+wCeOeMO
drixfFNicVpKY2l05LPSynw=
=NAy9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-17 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 17:22 [PATCH][2011.003-maintenance] ti-pru-sw-example: fix building with new toolchain sysroot Chase Maupin
2011-03-16 18:22 ` Koen Kooi
2011-03-16 18:56 ` Maupin, Chase
2011-03-16 19:02 ` Maupin, Chase
2011-03-17 7:44 ` Koen Kooi [this message]
2011-03-17 14:01 ` 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='ilse5o$fd4$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.