> I'm all for finding the best technical solution in the end, but I wonder > if we can at least come to an intermediate solution for the upcoming > release so that folks do not need to carry too many extra patches in > their pipelines > (https://patchwork.kernel.org/project/cip-dev/patch/cf43e9da3cfc59771e801d3215d3b3794f3602a8.1763446144.git.jan.kis...@siemens.com/)
I am not sure why point to patch v4 but I did provide the final path version that T.F. should be ok with. https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/ What this delay is that there are several feature coverage on the same file. Meanwhile, there are several similar patches pushed and T.F. action time is a bit slow. The very first patch was almost two months ago. https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/ So I had no clue why that huge delay. BTW it is supposed to revert that pointed out patch to easily fix things. Brian
