On 19/12/2022 16:17, Matthias Brugger wrote: > > > On 19/12/2022 14:44, Rob Herring wrote: >> On Wed, Dec 7, 2022 at 3:49 AM Moudy Ho <moudy.ho@xxxxxxxxxxxx> wrote: >>> >>> For MT8195, VPPSYS0 and VPPSYS1 are 2 display pipes with >>> hardware differences in power domains, clocks and subsystem counts, >>> which should be determined by compatible names. >>> >>> Signed-off-by: Moudy Ho <moudy.ho@xxxxxxxxxxxx> >>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> >>> --- >>> .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml | 5 ++++- >>> 1 file changed, 4 insertions(+), 1 deletion(-) >> >> This landed in today's linux-next causing the following binding >> warnings. Is this a fix? Only fixes for 6.2 should be added during the >> merge window. >> > > No it's not a fix, it's queued for the next -rc phase. I didn't know of the > limitation of linux-next only allowing fixes in the merge window. Stephen asks for it every time. Now it is in separate email: https://lore.kernel.org/linux-next/20221213120359.47fc3cad@xxxxxxxxxxxxxxxx/ Previously it was in each linux-next announcement: https://lore.kernel.org/linux-next/20220527164940.6ef5b25e@xxxxxxxxxxxxxxxx/ > > Actually the patch is wrong. It shouldn't include "mediatek,mt8195-mmsys" as > fallback for mediatek,mt8195-vppsys[0,1]. > > I'll revert the whole series from v6.2-tmp/dts64 and v6.2-tmp/soc Thanks. Please, drop all material for next cycle from linux-next. Best regards, Krzysztof
