On Thu, Oct 17, 2024 at 09:17:23PM +0300, Dmitry Baryshkov wrote: > Document compatible for the IPCC mailbox controller on SAR2130P platform. > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml | 1 + > 1 file changed, 1 insertion(+) Jassi, the patch is trivial, is has been reviewed by the DT maintainers almost a month ago, but it is still not a part of the -next. We are past -rc7, so we should not expect new patches coming into the for-next branches. The mailbox/for-next tree has been updated 7 weeks ago. Are there no pending patches for the mailbox tree? It is expected that the kernel tree is at least a bit tested before the trees get sent for -rc1. I see that it is a typical cadence for your tree, the patches get picked up after one of the last -rc releases. Can we help you somehow in order to improve it? Even putting the testing / conflicts / linux-next point of view aside, being unsure until the last -rc whether the patch gets accepted or not is not that nice from the developer's point of view. > > diff --git a/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml b/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml > index 2d66770ed3612fd4bf9e28c334b273033e13684f..ecb4ec1e0a82856581f16391813b3c533c4f6f90 100644 > --- a/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml > +++ b/Documentation/devicetree/bindings/mailbox/qcom-ipcc.yaml > @@ -28,6 +28,7 @@ properties: > - qcom,qdu1000-ipcc > - qcom,sa8255p-ipcc > - qcom,sa8775p-ipcc > + - qcom,sar2130p-ipcc > - qcom,sc7280-ipcc > - qcom,sc8280xp-ipcc > - qcom,sdx75-ipcc > > --- > base-commit: 7df1e7189cecb6965ce672e820a5ec6cf499b65b > change-id: 20241017-sar2130p-mbox-1ff72d8eb5c8 > > Best regards, > -- > Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> > -- With best wishes Dmitry
