devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	linux-arm-msm@vger.kernel.org, Lee Jones <lee@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: [PATCH 3/3] dt-bindings: mfd: qcom,spmi-pmic: use generic node name "gpio"
Date: Mon, 12 Sep 2022 16:41:15 -0500	[thread overview]
Message-ID: <20220912214115.GA1948286-robh@kernel.org> (raw)
In-Reply-To: <20220908080938.29199-3-krzysztof.kozlowski@linaro.org>

On Thu, 08 Sep 2022 10:09:38 +0200, Krzysztof Kozlowski wrote:
> GPIO controller nodes are named by convention just "gpio", not "gpios".
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>  Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 

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

  reply	other threads:[~2022-09-12 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  8:09 [PATCH 1/3] ARM: dts: qcom: use generic node name "gpio" in SPMI PMIC Krzysztof Kozlowski
2022-09-08  8:09 ` [PATCH 2/3] arm64: " Krzysztof Kozlowski
2022-09-08  8:09 ` [PATCH 3/3] dt-bindings: mfd: qcom,spmi-pmic: use generic node name "gpio" Krzysztof Kozlowski
2022-09-12 21:41   ` Rob Herring [this message]
2022-09-28  9:41   ` Lee Jones
2022-09-28 11:05     ` Krzysztof Kozlowski
2022-09-29 16:52       ` Lee Jones
2022-10-24 12:54   ` Lee Jones
2022-10-18  3:05 ` (subset) [PATCH 1/3] ARM: dts: qcom: use generic node name "gpio" in SPMI PMIC Bjorn Andersson

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=20220912214115.GA1948286-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@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 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).