From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Rohit Agarwal <quic_rohiagar@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, linus.walleij@linaro.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: pinctrl: qcom-pmic-gpio: Add pm7550ba support
Date: Thu, 6 Jul 2023 16:35:21 +0200 [thread overview]
Message-ID: <4042fa22-8948-49c9-6e5c-dc8926ed5f99@linaro.org> (raw)
In-Reply-To: <1688650209-25119-2-git-send-email-quic_rohiagar@quicinc.com>
On 06/07/2023 15:30, Rohit Agarwal wrote:
> Add support for the pm7550ba GPIO support to the Qualcomm PMIC GPIO
> binding.
>
> Signed-off-by: Rohit Agarwal <quic_rohiagar@quicinc.com>
> ---
> Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml | 3 +++
I doubt that all your patches here and other patchsets are v1. Otherwise
how did you get my Acks and Rbs? Please use proper versioning and
provide changelog.
What changed here?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-06 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 13:30 [PATCH 0/4] Add support for pinctrl in pmic chips Rohit Agarwal
2023-07-06 13:30 ` [PATCH 1/4] dt-bindings: pinctrl: qcom-pmic-gpio: Add pm7550ba support Rohit Agarwal
2023-07-06 14:35 ` Krzysztof Kozlowski [this message]
2023-07-06 14:45 ` Rohit Agarwal
2023-07-06 15:04 ` Konrad Dybcio
2023-07-06 15:11 ` Rohit Agarwal
2023-07-06 15:23 ` Konrad Dybcio
2023-07-06 15:29 ` Rohit Agarwal
2023-07-06 13:30 ` [PATCH 2/4] dt-bindings: pinctrl: qcom-pmic-gpio: Add pmx75 support Rohit Agarwal
2023-07-06 13:30 ` [PATCH 3/4] pinctrl: qcom-pmic-gpio: Add support for pm7550ba Rohit Agarwal
2023-07-06 13:30 ` [PATCH 4/4] pinctrl: qcom-pmic-gpio: Add support for pmx75 Rohit Agarwal
2023-07-06 15:02 ` [PATCH 0/4] Add support for pinctrl in pmic chips Konrad Dybcio
2023-07-06 15:09 ` Rohit Agarwal
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=4042fa22-8948-49c9-6e5c-dc8926ed5f99@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_rohiagar@quicinc.com \
--cc=robh+dt@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).