Re: [PATCH v8 04/12] dt-bindings: npu: rockchip: add rockchip,rk3576-rknn-core
Jiaxing Hu <[email protected]>
| Newsgroups | org.infradead.lists.linux-rockchip,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
Hi Rob, Taking the last paragraph first, since that is the actionable one. In v9 the dependency will be in the patch itself, as a git note that format-patch carries below the ---, rather than only in the cover letter where it is now. It says the patch touches only Documentation and applies to v7.2 on its own, and that the series it belongs to is based on next-20260814 plus Igor Paunovic's "[PATCH v2] accel/rocket: request the core clocks by name", which the driver patches need and this one does not. https://lore.kernel.org/linux-rockchip/[email protected]/ I re-ran dt_binding_check after your mail, on the three bindings this series touches, with dtschema 2026.6, which is the current release on PyPI, and yamllint 1.38.0. npu/rockchip,rk3588-rknn-core.yaml clean power/rockchip,power-controller.yaml clean iommu/rockchip,iommu.yaml clean None of the three reports in your mail is in a file this patch touches. The unresolvable reference is in mfd/qcom,spmi-pmic.yaml, and the refcheckdocs hits are in two translations and arch/arm/xen/enlighten.c. I mention it only so it is clear I read them rather than assumed, not to argue the bot was wrong to print them. v9 is not posted yet, so please read the note as what it will carry and not as done. I am holding it because v8 drew three reviewers within a day of going out and I would rather collect the rest of that than reset the thread. Say the word if you would prefer the respin now and I will send it. Regards, Jiaxing _______________________________________________ Linux-rockchip mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-rockchip