From: kernel-hacker@bennee.com
To: openembedded-devel@lists.openembedded.org
Subject: A few fixes (resend, hopefully not munged this time)
Date: Thu, 12 Aug 2010 16:35:34 +0100 [thread overview]
Message-ID: <1281627336-686-1-git-send-email-kernel-hacker@bennee.com> (raw)
Hi,
Sorry for the delay resubmitting these. Please find attached the
following patches we added to OE during bringing up our tree. Our
actual patch series runs to around 14 patches but I assume your not
interested in more non-consumer boards or patches that "work for us".
However I'm happy to send them to the mailing list or privately if
someone wants to review them. A number of the patches were from Phil
Blundel and I believe have already worked their way upstream from his
trees.
[PATCH 1/2] freetype: include perl-native dependancy
[PATCH 2/2] recode: Fix configure step.
--
Alex.
next reply other threads:[~2010-08-12 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 15:35 kernel-hacker [this message]
2010-08-12 15:35 ` [PATCH 1/2] freetype: include perl-native dependancy kernel-hacker
2010-08-12 17:04 ` Tom Rini
2010-08-12 17:23 ` Alex Bennee
2010-08-12 18:57 ` Tom Rini
2010-08-12 15:35 ` [PATCH 2/2] recode: Fix configure step kernel-hacker
2010-08-12 17:05 ` Tom Rini
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=1281627336-686-1-git-send-email-kernel-hacker@bennee.com \
--to=kernel-hacker@bennee.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.