On Sat, Dec 4, 2021 at 1:59 AM Srinivasa Rao Mandadapu <srivasam@xxxxxxxxxxxxxx> wrote: > > > On 12/4/2021 5:08 AM, Rob Herring wrote: > Thanks for your time and notifying the issue!!! > > On Fri, Dec 3, 2021 at 5:34 PM Rob Herring <robh@xxxxxxxxxx> wrote: > >> On Fri, 03 Dec 2021 21:37:37 +0530, Srinivasa Rao Mandadapu wrote: > >>> From: Srinivasa Rao Mandadapu <srivasam@xxxxxxxxxxxxxx> > >>> > >>> Add bindings for sc7280 lpass cpu driver which supports > >>> audio over i2s based speaker, soundwire based headset, msm dmics > >>> and HDMI Port. > >>> > >>> Signed-off-by: Srinivasa Rao Mandadapu <srivasam@xxxxxxxxxxxxxx> > >>> Co-developed-by: Venkata Prasad Potturu <potturu@xxxxxxxxxxxxxx> > >>> Signed-off-by: Venkata Prasad Potturu <potturu@xxxxxxxxxxxxxx> > >>> --- > >>> .../devicetree/bindings/sound/qcom,lpass-cpu.yaml | 70 +++++++++++++++++++--- > >>> 1 file changed, 62 insertions(+), 8 deletions(-) > >>> > >> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > >> on your patch (DT_CHECKER_FLAGS is new in v5.13): > >> > >> yamllint warnings/errors: > >> > >> dtschema/dtc warnings/errors: > >> /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/sound/qcom,lpass-cpu.example.dt.yaml: lpass@62d80000: reg: [[0, 1658351616, 0, 425984], [0, 1659895808, 0, 167936]] is too short > >> From schema: /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/sound/qcom,lpass-cpu.yaml > > Are you running the checks before you send out your patches. Because > > it seems like you keep sending things with the same errors. > > > > If there's errors, I'm not going to review this. If you need help > > getting it to work, then ask. > Actually, the too short name errors are coming for the existing names > also. could you please suggest on how to go ahead? Go read Documentation/devicetree/bindings/example-schema.yaml and the part about default address sizes. > > > > And what's with your email setup? codeaurora.com bounces. > > From December 3 Qualcomm mail domain got changed to quicinc.com from > codeaurora.org. > > May be that's the reason for bouncing. No idea. Just fix it please. I don't think I've seen this problem from anyone else. Rob
