All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH 2/2] dt-bindings: vexpress-sysreg: Allow for no child nodes
Date: Fri, 17 Jun 2022 13:14:53 -0600	[thread overview]
Message-ID: <20220617191453.GA2126159-robh@kernel.org> (raw)
In-Reply-To: <20220613171809.3928949-2-robh@kernel.org>

On Mon, 13 Jun 2022 11:18:08 -0600, Rob Herring wrote:
> It is valid for arm,vexpress-sysreg to have no child nodes when either
> the deprecated binding without child nodes is used or a platform
> has no GPIOs. If there are no child nodes, then "#address-cells" and
> "#size-cells" should not be required. However, "reg" should be present
> in all cases, so let's add it now.
> 
> Cc: Andre Przywara <andre.przywara@arm.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
>  Documentation/devicetree/bindings/arm/vexpress-sysreg.yaml | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 

Applied, thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Andre Przywara <andre.przywara@arm.com>
Subject: Re: [PATCH 2/2] dt-bindings: vexpress-sysreg: Allow for no child nodes
Date: Fri, 17 Jun 2022 13:14:53 -0600	[thread overview]
Message-ID: <20220617191453.GA2126159-robh@kernel.org> (raw)
In-Reply-To: <20220613171809.3928949-2-robh@kernel.org>

On Mon, 13 Jun 2022 11:18:08 -0600, Rob Herring wrote:
> It is valid for arm,vexpress-sysreg to have no child nodes when either
> the deprecated binding without child nodes is used or a platform
> has no GPIOs. If there are no child nodes, then "#address-cells" and
> "#size-cells" should not be required. However, "reg" should be present
> in all cases, so let's add it now.
> 
> Cc: Andre Przywara <andre.przywara@arm.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
>  Documentation/devicetree/bindings/arm/vexpress-sysreg.yaml | 3 +--
>  1 file changed, 1 insertion(+), 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:[~2022-06-17 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 17:18 [PATCH 1/2] dt-bindings: vexpress-sysreg: Add deprecated GPIO provider properties Rob Herring
2022-06-13 17:18 ` Rob Herring
2022-06-13 17:18 ` [PATCH 2/2] dt-bindings: vexpress-sysreg: Allow for no child nodes Rob Herring
2022-06-13 17:18   ` Rob Herring
2022-06-17 19:14   ` Rob Herring [this message]
2022-06-17 19:14     ` Rob Herring
2022-06-17 19:14 ` [PATCH 1/2] dt-bindings: vexpress-sysreg: Add deprecated GPIO provider properties Rob Herring
2022-06-17 19:14   ` 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=20220617191453.GA2126159-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.