All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	devicetree@vger.kernel.org, Wen He <wen.he_1@nxp.com>
Subject: Re: [PATCH 2/2] dt/bindings: clk: fsl,plldig: Drop 'bindings' from schema id
Date: Mon, 3 Feb 2020 09:39:46 +0000	[thread overview]
Message-ID: <CAL_JsqJObO2AgP6m_=Z=7eWHA7C6q-Vrv20v08h_r0EL4pOfAg@mail.gmail.com> (raw)
In-Reply-To: <20200203052507.93215-2-sboyd@kernel.org>

On Mon, Feb 3, 2020 at 5:25 AM Stephen Boyd <sboyd@kernel.org> wrote:
>
> Having 'bindings' in here causes a warning when checking the schema.
>
>  Documentation/devicetree/bindings/clock/fsl,plldig.yaml:
>  $id: relative path/filename doesn't match actual path or filename
>          expected: http://devicetree.org/schemas/clock/fsl,plldig.yaml#
>
> Remove it.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Wen He <wen.he_1@nxp.com>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> ---
>  Documentation/devicetree/bindings/clock/fsl,plldig.yaml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

There's actually a more few of these in clock bindings. I am going to
do a tree wide fix on this. I was waiting until the clock tree is
merged.

And I didn't really mean to commit this check to dtschema until all
these were fixed, so I've reverted it for now.

So either go ahead and apply this or I'll get it.

Acked-by: Rob Herring <robh@kernel.org>

Rob

  reply	other threads:[~2020-02-03  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  5:25 [PATCH 1/2] clk: ls1028a: Fix warning on clamp() usage Stephen Boyd
2020-02-03  5:25 ` [PATCH 2/2] dt/bindings: clk: fsl,plldig: Drop 'bindings' from schema id Stephen Boyd
2020-02-03  9:39   ` Rob Herring [this message]
2020-02-03 18:33   ` Stephen Boyd
2020-02-03 18:33 ` [PATCH 1/2] clk: ls1028a: Fix warning on clamp() usage Stephen Boyd

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='CAL_JsqJObO2AgP6m_=Z=7eWHA7C6q-Vrv20v08h_r0EL4pOfAg@mail.gmail.com' \
    --to=robh+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=wen.he_1@nxp.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.