From: patchwork-bot+linux-arm-msm@kernel.org
To: Doug Anderson <dianders@chromium.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v7 1/4] pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0
Date: Mon, 01 Mar 2021 19:59:43 +0000 [thread overview]
Message-ID: <161462878304.6187.3950456849874918154.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210114191601.v7.1.I3ad184e3423d8e479bc3e86f5b393abb1704a1d1@changeid>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Thu, 14 Jan 2021 19:16:21 -0800 you wrote:
> There's currently a comment in the code saying function 0 is GPIO.
> Instead of hardcoding it, let's add a member where an SoC can specify
> it. No known SoCs use a number other than 0, but this just makes the
> code clearer. NOTE: no SoC code needs to be updated since we can rely
> on zero-initialization.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> Reviewed-by: Maulik Shah <mkshah@codeaurora.org>
> Tested-by: Maulik Shah <mkshah@codeaurora.org>
> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>
> [...]
Here is the summary with links:
- [v7,1/4] pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0
https://git.kernel.org/qcom/c/a82e537807d5
- [v7,2/4] pinctrl: qcom: No need to read-modify-write the interrupt status
https://git.kernel.org/qcom/c/4079d35fa4fc
- [v7,3/4] pinctrl: qcom: Properly clear "intr_ack_high" interrupts when unmasking
https://git.kernel.org/qcom/c/a95881d6aa2c
- [v7,4/4] pinctrl: qcom: Don't clear pending interrupts when enabling
https://git.kernel.org/qcom/c/cf9d052aa600
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-01 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 3:16 [PATCH v7 1/4] pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0 Douglas Anderson
2021-01-15 3:16 ` [PATCH v7 2/4] pinctrl: qcom: No need to read-modify-write the interrupt status Douglas Anderson
2021-01-15 3:16 ` [PATCH v7 3/4] pinctrl: qcom: Properly clear "intr_ack_high" interrupts when unmasking Douglas Anderson
2021-01-15 3:16 ` [PATCH v7 4/4] pinctrl: qcom: Don't clear pending interrupts when enabling Douglas Anderson
2021-01-15 3:19 ` Stephen Boyd
2021-01-18 15:07 ` [PATCH v7 1/4] pinctrl: qcom: Allow SoCs to specify a GPIO function that's not 0 Linus Walleij
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [this message]
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=161462878304.6187.3950456849874918154.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox