[U-Boot] [PATCH v2 2/2] dm: MIGRATION: Update migration plan for DM_SPI_FLASH

[Simon Glass]

Hi Jagan,

On Tue, 1 Jan 2019 at 12:17, Jagan Teki <jagan at amarulasolutions.com> wrote:
>
> Migration plan for DM_SPI_FLASH is v2019.07 since it
> depends on DM_SPI migration.
>
> Signed-off-by: Jagan Teki <jagan at amarulasolutions.com>
> ---
> Changes for v2:
> - none
>
>  Makefile | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index c4d827f259..3e926d839f 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -964,6 +964,16 @@ ifneq ($(CONFIG_DM_SPI)$(CONFIG_OF_CONTROL),yy)
>         @echo >&2 "See doc/driver-model/MIGRATION.txt for more info."
>         @echo >&2 "===================================================="
>  endif
> +endif
> +ifeq ($(CONFIG_SPI_FLASH),y)

Again i worry what happens if the board does not actually use SPI flash?

> +ifneq ($(CONFIG_DM_SPI_FLASH)$(CONFIG_OF_CONTROL),yy)
> +       @echo >&2 "===================== WARNING ======================"
> +       @echo >&2 "This board does not use CONFIG_DM_SPI_FLASH. Please update"
> +       @echo >&2 "the board to use CONFIG_SPI_FLASH before the v2019.07 release."
> +       @echo >&2 "Failure to update by the deadline may result in board removal."
> +       @echo >&2 "See doc/driver-model/MIGRATION.txt for more info."
> +       @echo >&2 "===================================================="
> +endif
>  endif
>         @# Check that this build does not use CONFIG options that we do not
>         @# know about unless they are in Kconfig. All the existing CONFIG
> --
> 2.18.0.321.gffc6fa0e3
>

Regards,
Simon