All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH v2] dt-bindings: bus: uniphier-system-bus: fix warning in example
Date: Mon, 29 Jun 2020 15:20:51 -0600	[thread overview]
Message-ID: <20200629212051.GA2925150@bogus> (raw)
In-Reply-To: <20200623113242.779241-1-yamada.masahiro@socionext.com>

On Tue, 23 Jun 2020 20:32:42 +0900, Masahiro Yamada wrote:
> Since commit e69f5dc623f9 ("dt-bindings: serial: Convert 8250 to
> json-schema"), the schema for "ns16550a" is checked.
> 
> 'make dt_binding_check' emits the following warning:
> 
>   uart@5,00200000: $nodename:0: 'uart@5,00200000' does not match '^serial(@[0-9a-f,]+)*$'
> 
> Rename the node to follow the pattern defined in
> Documentation/devicetree/bindings/serial/serial.yaml
> 
> While I was here, I removed leading zeros from unit names.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
> 
> Changes in v2:
>  - change unit names too
> 
>  .../bindings/bus/socionext,uniphier-system-bus.yaml           | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 

Applied, thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] dt-bindings: bus: uniphier-system-bus: fix warning in example
Date: Mon, 29 Jun 2020 15:20:51 -0600	[thread overview]
Message-ID: <20200629212051.GA2925150@bogus> (raw)
In-Reply-To: <20200623113242.779241-1-yamada.masahiro@socionext.com>

On Tue, 23 Jun 2020 20:32:42 +0900, Masahiro Yamada wrote:
> Since commit e69f5dc623f9 ("dt-bindings: serial: Convert 8250 to
> json-schema"), the schema for "ns16550a" is checked.
> 
> 'make dt_binding_check' emits the following warning:
> 
>   uart@5,00200000: $nodename:0: 'uart@5,00200000' does not match '^serial(@[0-9a-f,]+)*$'
> 
> Rename the node to follow the pattern defined in
> Documentation/devicetree/bindings/serial/serial.yaml
> 
> While I was here, I removed leading zeros from unit names.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
> 
> Changes in v2:
>  - change unit names too
> 
>  .../bindings/bus/socionext,uniphier-system-bus.yaml           | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 

Applied, thanks!

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

  reply	other threads:[~2020-06-29 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 11:32 [PATCH v2] dt-bindings: bus: uniphier-system-bus: fix warning in example Masahiro Yamada
2020-06-29 21:20 ` Rob Herring [this message]
2020-06-29 21:20   ` Rob Herring

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=20200629212051.GA2925150@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=yamada.masahiro@socionext.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.