dm: MIGRATION: Update migration plan for BLK
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. Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com>
This commit is contained in:
parent
ea9d7c17fc
commit
7cfc1a381e
@ -39,14 +39,12 @@ CONFIG_BLK
|
||||
----------
|
||||
|
||||
Status: In progress
|
||||
Deadline: 2018.05
|
||||
Deadline: 2019.07
|
||||
|
||||
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.
|
||||
|
||||
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
|
||||
|
Loading…
Reference in New Issue
Block a user