devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: john@phrozen.org, neil@brown.name, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] dt-bindings: bus: add palmbus device tree bindings
Date: Mon, 18 Oct 2021 11:54:52 -0500	[thread overview]
Message-ID: <YW2m3DOv6TvHm2l+@robh.at.kernel.org> (raw)
In-Reply-To: <20211016203323.9165-1-sergio.paracuellos@gmail.com>

On Sat, 16 Oct 2021 22:33:23 +0200, Sergio Paracuellos wrote:
> Add device tree bindings for palmbus controller present in all the MIPS
> ralink based SoCs.
> 
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> changes in v5: Sent wrong patch in v4. Hence, properly sent it.
> Changes in v4: The node name pattern is already checked elsewhere. There is only need to
>                define the unit-address part which should be lowercase hex.
> Changes in v3: change sample to use child node which its bindings are
>                already in YAML format to make dtschema happier.
> Changes in v2: fixed missing semicolon in example.
>  .../devicetree/bindings/bus/palmbus.yaml      | 79 +++++++++++++++++++
>  1 file changed, 79 insertions(+)
>  .../devicetree/bindings/bus/palmbus.yaml      | 79 +++++++++++++++++++
>  1 file changed, 79 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/bus/palmbus.yaml
> 

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

  reply	other threads:[~2021-10-18 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-16 20:33 [PATCH v5] dt-bindings: bus: add palmbus device tree bindings Sergio Paracuellos
2021-10-18 16:54 ` Rob Herring [this message]
2021-10-18 16:57 ` 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=YW2m3DOv6TvHm2l+@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=sergio.paracuellos@gmail.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).