From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Fix uImage generation in way compatible with kernel.bbclass
Date: Thu, 29 Nov 2007 11:29:47 +0000 [thread overview]
Message-ID: <20071129112947.1fd36922@openmoko> (raw)
In-Reply-To: <474D5541.2020107@xora.org.uk>
On Wed, 28 Nov 2007 11:47:13 +0000
Graeme Gregory <dp@xora.org.uk> wrote:
> I would like to do the attached patch to linux.inc to change uImage
> generation so it is compatible with the way kernel.bbclass does
> things.
>
> This means the uImage ends up in kernel-image not some random file
> called uImage but not really a uImage.
>
> koen said the do_install_prepend stuff was to work around vendor bugs
> and is no longer needed in this file.
>
I think we have knocked down all the objections by email now?
Shall I apply?
Graeme
prev parent reply other threads:[~2007-11-29 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 11:47 [RFC] Fix uImage generation in way compatible with kernel.bbclass Graeme Gregory
2007-11-28 13:43 ` Koen Kooi
2007-11-28 14:32 ` Graeme Gregory
2007-11-28 14:36 ` Graeme Gregory
2007-11-28 15:55 ` Koen Kooi
2007-11-28 17:16 ` Graeme Gregory
2007-11-28 14:49 ` pHilipp Zabel
2007-11-29 11:29 ` Graeme Gregory [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=20071129112947.1fd36922@openmoko \
--to=dp@xora.org.uk \
--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.