All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] remove duplicated code from linux.inc
Date: Thu, 30 Jul 2009 09:59:30 +0100	[thread overview]
Message-ID: <4A7160F2.8030000@xora.org.uk> (raw)
In-Reply-To: <6ec4247d0907292249k42c582ddid3d53e847c5f835d@mail.gmail.com>

Graham Gower wrote:
> 2009/7/30 Tom Rini <trini@embeddedalley.com>:
>   
>> That should work.
>>     
>
> Could you show me how?
> I have tried, but the ${UBOOT_ENTRYPOINT} used by either linux.inc or
> kernel.bbclass is parsed and put into the run.do_foo file before the
> symbol searching occurs.
>
>   
Why dont you prepend it to the current uImage creation code running only 
conditionally on UBOOT_ENTRYSYMBOL being set? As its in the same bit of 
shell code your resetting of UBOOT_ENTRYPOINT will take precedence! Also 
means other machines can use it.

Graeme




  reply	other threads:[~2009-07-30  9:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  4:30 [PATCH] remove duplicated code from linux.inc Graham Gower
2009-07-29  7:34 ` Koen Kooi
2009-07-29  8:36   ` Marcin Juszkiewicz
2009-07-29  8:38   ` Graeme Gregory
2009-07-29  9:31     ` Marcin Juszkiewicz
2009-07-30  5:11       ` Graham Gower
2009-07-30  5:33         ` Tom Rini
2009-07-30  5:49           ` Graham Gower
2009-07-30  8:59             ` Graeme Gregory [this message]
2009-07-31  2:24               ` Graham Gower
2009-07-31  7:12                 ` Graeme Gregory
2009-07-31  7:40                   ` Graham Gower
2009-07-31  8:55                     ` Graeme Gregory
2009-07-31  9:59                     ` Koen Kooi
2009-07-31 11:33                     ` Graeme Gregory
2009-07-31 12:35                       ` Graham Gower
2009-07-31 13:24                         ` Marcin Juszkiewicz
2009-08-01  9:45                           ` Graham Gower
2009-08-03  6:54                             ` Marcin Juszkiewicz
2009-07-31 17:45                       ` Koen Kooi
2009-07-31  7:50                   ` Andrea Adami
2009-07-31  9:03                     ` Graham Gower

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=4A7160F2.8030000@xora.org.uk \
    --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.