From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot.inc: make sure all counter variables are properly unset
Date: Thu, 23 Apr 2015 20:31:00 +0200 [thread overview]
Message-ID: <55393A64.4050800@pseudoterminal.org> (raw)
In-Reply-To: <CAP9ODKoikygfbhSMMHUk9pPHhvbM9vav_ArAZ7gufTm5s0H_SA@mail.gmail.com>
It is in master, which is nice. But not in fido? Is it too late for
fixes like these? If so, I'll have to backport this fix into
meta-fsl-arm-extra for the cubox-i uboot.
Otherwise, if it is to be reviewed for inclusion into fido, I'm fine
with that.
Am 2015-04-20 um 21:31 schrieb Otavio Salvador:
> On Mon, Apr 20, 2015 at 4:17 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> The script does "i == j" checks to retrieve the config <-> type pairs from
>> the UBOOT_MACHINE and UBOOT_CONFIG lists. This check however requires both
>> j and i to be initially unset. Ensure this by explicitely unsetting i.
>>
>> This fixes broken u-boot SPL installations with SolidRun machines
>> (the SPL wasn't being installed and deployed.)
>>
>> Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
> Acked-by: Otavio Salvador <otavio@ossystems.com.br>
>
> Richard, this needs to be applied into master and fido branches.
>
next prev parent reply other threads:[~2015-04-23 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 19:17 [PATCH] u-boot.inc: make sure all counter variables are properly unset Carlos Rafael Giani
2015-04-20 19:31 ` Otavio Salvador
2015-04-23 18:31 ` Carlos Rafael Giani [this message]
2015-04-23 18:33 ` Otavio Salvador
2015-04-21 23:22 ` 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=55393A64.4050800@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.