[U-Boot] [RFC for-v2019.01 4/4] dm: MIGRATION: Update migration plan for BLK

[Simon Glass]

Hi Tom,

On Sun, 25 Nov 2018 at 11:19, Tom Rini <trini at konsulko.com> wrote:
>
> The biggest part of migration to using CONFIG_BLK is that we need to
> have the various subsystems migrated first, so reword the plan here to
> reference the new deadlines.
>
> Cc: Simon Glass <sjg at chromium.org>
> Signed-off-by: Tom Rini <trini at konsulko.com>
> ---
>  doc/driver-model/MIGRATION.txt | 12 +++++-------
>  1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/doc/driver-model/MIGRATION.txt b/doc/driver-model/MIGRATION.txt
> index 6df7e02a63de..6b691338b4e7 100644
> --- a/doc/driver-model/MIGRATION.txt
> +++ b/doc/driver-model/MIGRATION.txt
> @@ -39,14 +39,12 @@ CONFIG_BLK
>  ----------
>
>  Status: In progress
> -Deadline: 2018.05
> -
> -Maintainers should submit patches for enabling CONFIG_BLK on all boards in
> -time for inclusion in the 2018.05 release. Boards not converted by this
> -time may be removed in a subsequent release.
> +Deadline: 2019.07
>
> -Note that this implies use of driver model for all block devices (e.g.
> -MMC, USB, SCSI, SATA).
> +In concert with maintainers migrating their block device usage to the
> +appropriate DM driver, CONFIG_BLK needs to be set as well.  The final deadline
> +here coincides with the final deadline for migration of the various block
> +subsystems.
>
>  CONFIG_DM_SPI
>  CONFIG_DM_SPI_FLASH
> --
> 2.7.4
>

My only concern here is the long deadline, more than a year after the
original one. Granted I should have been more proactive in sending
patches in May/June, but this has been fairly widely telegraphed IMO.
I know that opinions different on this matter.

I'm also concerned about dealing with the SPL size issues that are
likely to come up, but with two implementations these problems are
masked.

Can I suggest an earlier deadline of 2019.01 instead? That effectively
gives people until about March/April to send patches.

Regards,
Simon