From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] http://patchwork.ozlabs.org/patch/136415/ seems to break HUSH parser?
Date: Wed, 08 Feb 2012 07:30:05 +0100 [thread overview]
Message-ID: <4F32166D.9070208@denx.de> (raw)
In-Reply-To: <4F313C55.8000905@denx.de>
Hello Stefano,
Stefano Babic wrote:
> On 06/02/2012 23:43, Albert ARIBAUD wrote:
>> Hi,
>>
>
> Hi Albert,
>
>> Some time ago I have posted http://patchwork.ozlabs.org/patch/136368/
>> which adds HUSH parser to ED Mini V2. In itself, the change is only made
>> of three CONFIG defines.
>>
>> This patch has built cleanly and worked as expected until
>> http://patchwork.ozlabs.org/patch/136415/ was applied. Applying both
>> patches causes edminiv2 build to fail with
>>
>> uboot at lilith:~/src/u-boot-arm$ ./MAKEALL edminiv2
>> Configuring for edminiv2 board...
>> common/libcommon.o: In function `cread_line':
>> /home/uboot/src/u-boot-arm/common/main.c:717: undefined reference to
>> `get_ticks'
>> /home/uboot/src/u-boot-arm/common/main.c:717: undefined reference to
>> `get_tbclk'
>> /home/uboot/src/u-boot-arm/common/main.c:720: undefined reference to
>> `get_ticks'
>
> This is not a problem in your patch, but some SOCs have no
> implementation of the new and now accepted iunterface. I have sent
Yep, exactly!
> patches for i.MX35/i.mx5/i.mx31:
> http://patchwork.ozlabs.org/patch/139718/
Thanks!
> I have seen that other SOCs have the same issue, while kirchwood has
> introduced an empty implementation for such functions. We should fix all
> remaining arch.
Yes.
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2012-02-08 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 22:43 [U-Boot] http://patchwork.ozlabs.org/patch/136415/ seems to break HUSH parser? Albert ARIBAUD
2012-02-07 14:59 ` Stefano Babic
2012-02-08 6:30 ` Heiko Schocher [this message]
2012-02-07 21:10 ` Prafulla Wadaskar
2012-02-08 5:13 ` Prafulla Wadaskar
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=4F32166D.9070208@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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.