All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
	devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml
Date: Tue, 6 Oct 2020 10:52:07 -0500	[thread overview]
Message-ID: <20201006155207.GA2297951@bogus> (raw)
In-Reply-To: <20200930145537.GA2851296@bogus>

On Wed, Sep 30, 2020 at 09:55:37AM -0500, Rob Herring wrote:
> On Mon, Sep 28, 2020 at 05:51:55PM -0500, Suman Anna wrote:
> > Update the AM65x HwSpinlock example to fix couple of warnings
> > that started showing up after the conversion of K3 bindings to
> > YAML format in commit 66e06509aa37 ("dt-bindings: arm: ti:
> > Convert K3 board/soc bindings to DT schema").
> > 
> >  compatible: ['ti,am654'] is not valid under any of the given schemas (Possible causes of the failure):
> >  compatible: ['ti,am654'] is too short
> >  compatible:0: 'ti,am654' is not one of ['ti,am654-evm']
> > 
> > Also, fix one of the node names while at this.
> > 
> > Signed-off-by: Suman Anna <s-anna@ti.com>
> > ---
> >  .../devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml        | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Reviewed-by: Rob Herring <robh@kernel.org>

I guess this isn't dependent on k3.yaml, so I've applied it.

Rob

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
	devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml
Date: Tue, 6 Oct 2020 10:52:07 -0500	[thread overview]
Message-ID: <20201006155207.GA2297951@bogus> (raw)
In-Reply-To: <20200930145537.GA2851296@bogus>

On Wed, Sep 30, 2020 at 09:55:37AM -0500, Rob Herring wrote:
> On Mon, Sep 28, 2020 at 05:51:55PM -0500, Suman Anna wrote:
> > Update the AM65x HwSpinlock example to fix couple of warnings
> > that started showing up after the conversion of K3 bindings to
> > YAML format in commit 66e06509aa37 ("dt-bindings: arm: ti:
> > Convert K3 board/soc bindings to DT schema").
> > 
> >  compatible: ['ti,am654'] is not valid under any of the given schemas (Possible causes of the failure):
> >  compatible: ['ti,am654'] is too short
> >  compatible:0: 'ti,am654' is not one of ['ti,am654-evm']
> > 
> > Also, fix one of the node names while at this.
> > 
> > Signed-off-by: Suman Anna <s-anna@ti.com>
> > ---
> >  .../devicetree/bindings/hwlock/ti,omap-hwspinlock.yaml        | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Reviewed-by: Rob Herring <robh@kernel.org>

I guess this isn't dependent on k3.yaml, so I've applied it.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-06 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 22:51 [PATCH -next] dt-bindings: hwlock: omap: Fix warnings with k3.yaml Suman Anna
2020-09-28 22:51 ` Suman Anna
2020-09-30 14:55 ` Rob Herring
2020-09-30 14:55   ` Rob Herring
2020-10-06 15:52   ` Rob Herring [this message]
2020-10-06 15:52     ` Rob Herring
2020-10-06 16:16     ` Suman Anna
2020-10-06 16:16       ` Suman Anna
2020-10-26 21:02 ` patchwork-bot+linux-remoteproc

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=20201006155207.GA2297951@bogus \
    --to=robh@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=s-anna@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.