From: patchwork-bot+linux-arm-msm@kernel.org
To: John Stultz <john.stultz@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v6 1/3] pinctrl: qcom: Kconfig: Rework PINCTRL_MSM to be a depenency rather then a selected config
Date: Tue, 29 Dec 2020 20:15:31 +0000 [thread overview]
Message-ID: <160927293109.13751.538044877321880477.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201106042710.55979-1-john.stultz@linaro.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Fri, 6 Nov 2020 04:27:08 +0000 you wrote:
> This patch reworks PINCTRL_MSM to be a visible option, and
> instead of having the various SoC specific drivers select
> PINCTRL_MSM, this switches those configs to depend on
> PINCTRL_MSM.
>
> This is useful, as it will be needed in order to cleanly support
> having the qcom-scm driver, which pinctrl-msm calls into,
> configured as a module. Without this change, we would eventually
> have to add dependency lines to every config that selects
> PINCTRL_MSM, and that would becomes a maintenance headache.
>
> [...]
Here is the summary with links:
- [v6,1/3] pinctrl: qcom: Kconfig: Rework PINCTRL_MSM to be a depenency rather then a selected config
https://git.kernel.org/qcom/c/be117ca32261
- [v6,2/3] pinctrl: qcom: Allow pinctrl-msm code to be loadable as a module
https://git.kernel.org/qcom/c/38e86f5c2645
- [v6,3/3] firmware: QCOM_SCM: Allow qcom_scm driver to be loadable as a permenent module
https://git.kernel.org/qcom/c/d0511b5496c0
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:[~2020-12-29 20:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 4:27 [PATCH v6 1/3] pinctrl: qcom: Kconfig: Rework PINCTRL_MSM to be a depenency rather then a selected config John Stultz
2020-11-06 4:27 ` John Stultz
2020-11-06 4:27 ` [PATCH v6 2/3] pinctrl: qcom: Allow pinctrl-msm code to be loadable as a module John Stultz
2020-11-06 4:27 ` John Stultz
2020-11-10 13:34 ` Linus Walleij
2020-11-10 13:34 ` Linus Walleij
2020-11-06 4:27 ` [PATCH v6 3/3] firmware: QCOM_SCM: Allow qcom_scm driver to be loadable as a permenent module John Stultz
2020-11-06 4:27 ` John Stultz
2020-11-10 13:35 ` Linus Walleij
2020-11-10 13:35 ` Linus Walleij
2020-11-10 18:51 ` John Stultz
2020-11-10 18:51 ` John Stultz
2020-11-12 17:37 ` Will Deacon
2020-11-12 17:37 ` Will Deacon
2020-11-12 19:17 ` John Stultz
2020-11-12 19:17 ` John Stultz
2020-11-16 15:59 ` Thierry Reding
2020-11-16 15:59 ` Thierry Reding
2020-11-16 16:36 ` Will Deacon
2020-11-16 16:36 ` Will Deacon
2020-11-16 19:48 ` John Stultz
2020-11-16 19:48 ` John Stultz
2020-11-17 13:47 ` Thierry Reding
2020-11-17 13:47 ` Thierry Reding
2020-11-19 9:33 ` Will Deacon
2020-11-19 9:33 ` Will Deacon
2020-11-23 12:35 ` Linus Walleij
2020-11-23 12:35 ` Linus Walleij
2020-11-23 13:06 ` Will Deacon
2020-11-23 13:06 ` Will Deacon
2020-11-16 19:40 ` John Stultz
2020-11-16 19:40 ` John Stultz
2020-11-10 13:33 ` [PATCH v6 1/3] pinctrl: qcom: Kconfig: Rework PINCTRL_MSM to be a depenency rather then a selected config Linus Walleij
2020-11-10 13:33 ` Linus Walleij
2020-12-29 20:15 ` 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=160927293109.13751.538044877321880477.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=john.stultz@linaro.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 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.