Message ID | 20231031073859.25298-4-itoral@igalia.com |
---|---|
State | Accepted |
Commit | ebb2f6eea688b9ffa46527c3e7570b2c347497b8 |
Headers | show |
Series | None | expand |
On 31/10/2023 18:53, Maíra Canal wrote: > Hi, > > I would like to ask the device tree maintainers if you are willing > to take this through your tree or should I push the entire series > through drm-misc/drm-misc-next. You got the ack which answers this, doesn't it? Best regards, Krzysztof
On Tue, Oct 31, 2023 at 02:53:35PM -0300, Maíra Canal wrote: > I would like to ask the device tree maintainers if you are willing > to take this through your tree or should I push the entire series > through drm-misc/drm-misc-next. dt-binding patches almost never go through Rob's tree, usually that only happens as a last resort if subsystem maintainers let them fall through the cracks. Cheers, Conor.
diff --git a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml index dae55b8a267b..dc078ceeca9a 100644 --- a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml +++ b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml @@ -17,6 +17,7 @@ properties: compatible: enum: - brcm,2711-v3d + - brcm,2712-v3d - brcm,7268-v3d - brcm,7278-v3d