From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Glass <sjg@chromium.org>
Date: Thu, 22 Nov 2018 13:50:31 -0700
Subject: [U-Boot] [PATCH 68/93] arm: Remove am65x_evm_a53 board
In-Reply-To: <f19c7013-53be-5744-e9aa-69e554ea62db@ti.com>
References: <20181119155413.158098-1-sjg@chromium.org>
 <20181119155413.158098-69-sjg@chromium.org>
 <f19c7013-53be-5744-e9aa-69e554ea62db@ti.com>
Message-ID: <CAPnjgZ0hwRSV3SFTEdieKbwggCrqanROWFW59soUHAaZaLD74w@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
To: u-boot@lists.denx.de

Hi Lokesh,

On Mon, 19 Nov 2018 at 09:58, Lokesh Vutla <lokeshvutla@ti.com> wrote:
>
> Hi Simon,
>
> On 11/19/2018 9:23 PM, Simon Glass wrote:
> > This board has not been converted to CONFIG_DM_BLK by the deadline.
> > Remove it.
> >
> > Signed-off-by: Simon Glass <sjg@chromium.org>
>
> Not sure if this is by mistake, but I see CONFIG_BLK is enabled in both
> the configs. Am I missing something?
>
> ➜  u-boot git:(master) make am65x_evm_r5_defconfig;cat .config | grep BLK
> #
> # configuration written to .config
> #
> CONFIG_BLK=y
> CONFIG_SPL_BLK=y
>
> ➜  u-boot git:(master) make am65x_evm_a53_defconfig;cat .config | grep BLK
> #
> # configuration written to .config
> #
> CONFIG_BLK=y
> CONFIG_SPL_BLK=y
>

This was the result of my removing the default CONFIG_SPL_BLK=y in the
Kconfig, since it produced a smaller list of broken boards. But having
thought about it, it is not the right thing to do.

So your board should be fine. Sorry for the trouble.

Regards,
Simon