From mboxrd@z Thu Jan  1 00:00:00 1970
From: Fabio Estevam <festevam@gmail.com>
Date: Fri, 9 Mar 2018 07:42:54 -0300
Subject: [U-Boot] [PULL] Please pull u-boot-imx
In-Reply-To: <8a22d1f9-f91b-cc87-fd40-41c7eeb17479@denx.de>
References: <8a22d1f9-f91b-cc87-fd40-41c7eeb17479@denx.de>
Message-ID: <CAOMZO5B5tHcQsmaff6WGVWVRbMYAaUQiavUh0WzdqNVrCx7bdg@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Stefano,

On Fri, Mar 9, 2018 at 7:13 AM, Stefano Babic <sbabic@denx.de> wrote:
> Hi Tom,
>
> Fabio fixed a build issue yesterday. It is just a single patch, but it
> should be flow into the release. You can pick it udirectly p, but I have
> also applied to u-boot-imx to make things easier.

Troy made a good observation yesterday: he asked me if after applying
this patch the error is still shown when BOOT_FROM is not passed in
the cfg file.

I tested it and it does not.

So we have some options here that I would like to discuss:

1. Drop the error message completely. This message is only helpful for
developers during bring up phase

2. Understand better the problem and fix the parallel build issue

I think 1 can be done for the upcoming release as the negative effect
of breaking builds is worse than showing the lack of BOOT_FROM tag.

Option number 2 would require more time to implement.

If you like I can resent a v2 of option 1 where the error message is removed.

Please let me know your thoughts.

Thanks,

Fabio Estevam