From: Krzysztof Kozlowski <krzk@kernel.org>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Roger Quadros <rogerq@ti.com>, Suman Anna <s-anna@ti.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: soc: ti: ti,pruss: fix schema ID
Date: Thu, 17 Sep 2020 10:35:30 +0200 [thread overview]
Message-ID: <CAJKOXPfd9iWHDNo9v=COroD_wuYL0xmOkRt-63WS_7G3As=kXQ@mail.gmail.com> (raw)
In-Reply-To: <CAMxfBF5WWQX3ZH0YcRZ_N8q4njTdG-RA4eM+zyQwmK7tYvw6DQ@mail.gmail.com>
On Thu, 17 Sep 2020 at 10:32, Grzegorz Jaszczyk
<grzegorz.jaszczyk@linaro.org> wrote:
>
> On Thu, 17 Sep 2020 at 09:05, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >
> > Add missing '#' to fix schema errors:
> >
> > $id: 'http://devicetree.org/schemas/soc/ti/ti,pruss.yaml' does not match 'http://devicetree.org/schemas/.*\\.yaml#'
> > $schema: 'http://devicetree.org/meta-schemas/core.yaml' is not one of ['http://devicetree.org/meta-schemas/core.yaml#', 'http://devicetree.org/meta-schemas/base.yaml#']
> > Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml: ignoring, error in schema: $id
> >
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > ---
> > Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> > index cf7dc83f724f..037c51b2f972 100644
> > --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> > +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> > @@ -1,8 +1,8 @@
> > # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > %YAML 1.2
> > ---
> > -$id: http://devicetree.org/schemas/soc/ti/ti,pruss.yaml
> > -$schema: http://devicetree.org/meta-schemas/core.yaml
> > +$id: http://devicetree.org/schemas/soc/ti/ti,pruss.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
>
> I've double checked and "#" was present in the original patch sent and
> ack for upstream: https://patchwork.kernel.org/patch/11729649/
> It seems like something got wrong on linux-next but this is the only
> diff between original patch and one found in linux-next. Thank you for
> taking care of it.
Indeed that's weird. It must get lost when applying...
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-09-17 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 7:05 [PATCH] dt-bindings: soc: ti: ti,pruss: fix schema ID Krzysztof Kozlowski
2020-09-17 8:32 ` Grzegorz Jaszczyk
2020-09-17 8:35 ` Krzysztof Kozlowski [this message]
2020-09-17 14:57 ` Suman Anna
2020-09-17 18:04 ` santosh.shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJKOXPfd9iWHDNo9v=COroD_wuYL0xmOkRt-63WS_7G3As=kXQ@mail.gmail.com' \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=santosh.shilimkar@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).