[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABHD4K-_jmC512_ckmw66FppJHitkU8j-M9TQ316+M9zou3Fmg@mail.gmail.com>
Date: Fri, 3 Jul 2020 13:24:50 +0530
From: Amit Tomer <amittomer25@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: linux-kernel@...r.kernel.org,
Andreas Färber <afaerber@...e.de>,
Andre Przywara <andre.przywara@....com>,
cristian.ciocaltea@...il.com, Rob Herring <robh+dt@...nel.org>,
Vinod Koul <vkoul@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
devicetree@...r.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
dan.j.williams@...el.com, linux-actions@...ts.infradead.org
Subject: Re: [PATCH v5 01/10] dt-bindings: dmaengine: convert Actions Semi Owl
SoCs bindings to yaml
On Fri, Jul 3, 2020 at 12:48 PM Amit Tomer <amittomer25@...il.com> wrote:
>
> Hi Rob,
>
>
> > If you already ran 'make dt_binding_check' and didn't see the above
> > error(s), then make sure dt-schema is up to date:
> >
> > pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade
> >
> > Please check and re-submit.
>
> I wasn't able to reproduce it, even after updating the dt-schema.
> Kindly have a look at logs:
>
> https://pastebin.ubuntu.com/p/xTBNNyBdFv/
Looks like, dtschema even after upgrade pointing to older commit "6a941d46b9f5".
Wondering why it has not been pointing to latest commit "6a941d46b9f5"
After upgrading the pip version for python3, and upgrading the dt-schema again
https://pastebin.ubuntu.com/p/Rd9knQgvKH/
Issue is still reproduced.
Thanks
-Amit
Powered by blists - more mailing lists