From: Linus Walleij <linus.walleij@linaro.org>
To: Vinod Koul <vkoul@kernel.org>, John Stultz <john.stultz@linaro.org>
Cc: MSM <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] pinctrl: qcom: Add binding and driver for SDX55 pincontrol
Date: Tue, 10 Nov 2020 15:47:08 +0100 [thread overview]
Message-ID: <CACRpkdY=g4omnvgTzsBP6qwg7s8VYaFwChgAsJciQFS7SJ67jQ@mail.gmail.com> (raw)
In-Reply-To: <20201109062620.14566-1-vkoul@kernel.org>
On Mon, Nov 9, 2020 at 7:26 AM Vinod Koul <vkoul@kernel.org> wrote:
> This series add device tree binding documentation and driver for SDX55 SOC
> pincontroller.
>
> Changes in v3:
> - Add ack by Bjorn
> - Fix dt_binding_check errors
> - Add gpio ranges in binding
Excellent, patches applied for v5.11.
I also just applied John Stultz patches for modularizing the Qualcomm
drivers so there might be some need to patch up so this driver can
also modularize, check the result!
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-11-10 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 6:26 [PATCH v3 0/2] pinctrl: qcom: Add binding and driver for SDX55 pincontrol Vinod Koul
2020-11-09 6:26 ` [PATCH v3 1/2] dt-bindings: pinctrl: qcom: Add SDX55 pinctrl bindings Vinod Koul
2020-11-09 22:07 ` Rob Herring
2020-11-09 6:26 ` [PATCH v3 2/2] pinctrl: qcom: Add SDX55 pincontrol driver Vinod Koul
2020-11-09 10:21 ` Manivannan Sadhasivam
2020-11-10 14:47 ` Linus Walleij [this message]
2020-11-11 4:37 ` [PATCH v3 0/2] pinctrl: qcom: Add binding and driver for SDX55 pincontrol Vinod Koul
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm
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='CACRpkdY=g4omnvgTzsBP6qwg7s8VYaFwChgAsJciQFS7SJ67jQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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).