
On Mon, Mar 01, 2021 at 03:03:11PM +0100, Marek Behun wrote:
On Thu, 25 Feb 2021 15:39:09 -0500 Tom Rini trini@konsulko.com wrote:
Well, past migration deadline doesn't mean it can cause CI to fail. I'm just now throwing things out that are 2 years past the deadline, and we'll probably be doing that for a few releases.
Tom, I would like to send v4 without the CONFIG_DM #ifdefs.
tqma6s_wru4_mmc_defconfig is the only defconfig that defines CONFIG_DM=n
Since I do not have this board, I cannot work on converting it to DM.
I can either
- add patch removing this board from U-Boot to this patch series
- send patch removing this board as separate from this series and send this series only after the board is removed
- stick if #ifdefs
- try to use IS_ENABLED(CONFIG_DM), but this would need some extra patches into header files because of undefined references (we really don't want this)
- something different
How should I proceed?
You can say your series depends on: https://patchwork.ozlabs.org/project/uboot/patch/20210221010634.21310-42-tri... which drops tqma6s_wru4_mmc_defconfig and you should submit a PR against https://github.com/u-boot/u-boot/ which will trigger a CI run in Azure so you can see what else fails to build, or if that really is the only board that would fail to build, in this case. Thanks!