From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [STABLE][PATCH] linux-omap: sync everything with .dev
Date: Wed, 27 May 2009 19:25:17 +0200 [thread overview]
Message-ID: <gvjt1t$h21$1@ger.gmane.org> (raw)
In-Reply-To: <4A1D768E.4050101@balister.org>
On 27-05-09 19:21, Philip Balister wrote:
> Koen Kooi wrote:
>> [ This is only the diffstat, the complete 4 megabyte big patch is at
>> http://dominion.thruhere.net/koen/OE/0001-linux-omap-sync-everything-with-.dev.patch
>> ]
>>
>> linux-omap: sync everything with .dev
>> * also sync the machine files to match the kernels
>
> Koen,
>
> I patched .stable and tried building console-image. This build failed on
> omap3-sgx-modules. Is there a way we can avoid building this? I suspect
> I can make it build by reading the bb file and downloading something
> from the TI website, but I'd like stable to build without having to do
> that.
The sgx modules don't need any evil bits :) My plan was to update the
sgx modules and codec-engine, dmai, etc in seperate patches along the way.
regards,
Koen
prev parent reply other threads:[~2009-05-27 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 8:57 [STABLE][PATCH] linux-omap: sync everything with .dev Koen Kooi
2009-05-27 16:35 ` Tom Rini
2009-05-27 17:21 ` Philip Balister
2009-05-27 17:25 ` Koen Kooi [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='gvjt1t$h21$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.