Re: (subset) [PATCH 1/4] pinctrl: qcom: spmi-gpio: Add pm8226 compatibility

Re: (subset) [PATCH 1/4] pinctrl: qcom: spmi-gpio: Add pm8226 compatibility

[Dominik Kobinski]

I have sent a v2 of this series (https://patchwork.kernel.org/project/linux-arm-msm/list/?series=586091), but forgot to set this patch series to superseded. Sorry for the confusion.
The only change that was actually made to this patchset was the commit message to the [4/4] patch, as pointed out by Bjorn Andersson. There was also another patch added at the end of the v2 series, but I believe it doesn't concern this subsystem.
I'm not sure how it should be handled now. I am really sorry for not setting this series to superseded earlier and complicating the whole situation.

Regards,
Dominik Kobinski

Re: (subset) [PATCH 1/4] pinctrl: qcom: spmi-gpio: Add pm8226 compatibility

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

On Sat, Nov 27, 2021 at 01:26:31PM +0100, Dominik Kobinski wrote:
> I have sent a v2 of this series (https://patchwork.kernel.org/project/linux-arm-msm/list/?series=586091), but forgot to set this patch series to superseded. Sorry for the confusion.
> The only change that was actually made to this patchset was the commit message to the [4/4] patch, as pointed out by Bjorn Andersson. There was also another patch added at the end of the v2 series, but I believe it doesn't concern this subsystem.
> I'm not sure how it should be handled now. I am really sorry for not setting this series to superseded earlier and complicating the whole situation.

Since you didn't quote any context in your reply I'm not 100% sure what
this is all about, the message you're replying to is a pinctrl one but
the message is to me so I guess it's something I applied.  If there's
any changes needed in code that's already applied please send an
incremental patch with those changes.

Please also look at your mail client setup - it's not word wrapping
within paragraphs and for some reason it set a Reply-To with the message
ID of the message you're replying to which confuses things.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[PATCH 1/4] pinctrl: qcom: spmi-gpio: Add pm8226 compatibility

[Dominik Kobinski]

Add support for pm8226 SPMI GPIOs. The PMIC features
8 GPIOs, with no holes inbetween.

Suggested-by: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
Signed-off-by: Dominik Kobinski <dominikkobinski314@gmail.com>
---
 drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c b/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
index 5283d5e9e8bc..0f0102f38cbb 100644
--- a/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
+++ b/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
@@ -1159,6 +1159,7 @@ static const struct of_device_id pmic_gpio_of_match[] = {
 	/* pm8150l has 12 GPIOs with holes on 7 */
 	{ .compatible = "qcom,pm8150l-gpio", .data = (void *) 12 },
 	{ .compatible = "qcom,pmc8180c-gpio", .data = (void *) 12 },
+	{ .compatible = "qcom,pm8226-gpio", .data = (void *) 8 },
 	{ .compatible = "qcom,pm8350-gpio", .data = (void *) 10 },
 	{ .compatible = "qcom,pm8350b-gpio", .data = (void *) 8 },
 	{ .compatible = "qcom,pm8350c-gpio", .data = (void *) 9 },
-- 
2.34.0

Re: (subset) [PATCH 1/4] pinctrl: qcom: spmi-gpio: Add pm8226 compatibility

[Mark Brown]

On Tue, 23 Nov 2021 18:41:27 +0100, Dominik Kobinski wrote:
> Add support for pm8226 SPMI GPIOs. The PMIC features
> 8 GPIOs, with no holes inbetween.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[3/4] dt-bindings: regulator: qcom: spmi-regulator: Document pm8226 compatible
      commit: 76e95f331be09bac8764e971613439d294422d6e
[4/4] regulator: qcom_spmi: Add pm8226 regulators
      commit: f8843e5e2dc85dc6a546ec130d76be66e62abed6

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark