From: Bjorn Andersson <andersson@kernel.org>
To: Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/4] Add support for Milos LPASS LPI pinctrl
Date: Mon, 23 Mar 2026 20:56:19 -0500 [thread overview]
Message-ID: <177431737466.23057.7104535276234811171.b4-ty@kernel.org> (raw)
In-Reply-To: <20260306-milos-pinctrl-lpi-v1-0-086946dbb855@fairphone.com>
On Fri, 06 Mar 2026 15:22:14 +0100, Luca Weiss wrote:
> Add the bindings, driver, arm64 defconfig and dts bits to support the
> LPASS LPI pinctrl on the Qualcomm Milos SoC.
>
> The devicetree changes require the addition of GPR in milos.dtsi (as
> specified in the b4 deps), the pinctrl changes have no dependency.
>
>
> [...]
Applied, thanks!
[4/4] arm64: dts: qcom: milos: Add LPASS LPI pinctrl node
commit: e7554449e9a225ee77600eef6bf410561de0d568
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-03-24 1:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 14:22 Luca Weiss
2026-03-06 14:22 ` [PATCH 1/4] dt-bindings: pinctrl: qcom: Add Milos " Luca Weiss
2026-03-07 15:40 ` Krzysztof Kozlowski
2026-03-10 11:26 ` Linus Walleij
2026-03-06 14:22 ` [PATCH 2/4] pinctrl: qcom: Add Milos LPASS LPI TLMM Luca Weiss
2026-03-10 11:28 ` Linus Walleij
2026-03-10 12:27 ` Konrad Dybcio
2026-03-06 14:22 ` [PATCH 3/4] arm64: defconfig: Enable Milos LPASS LPI pinctrl driver Luca Weiss
2026-03-07 15:41 ` Krzysztof Kozlowski
2026-03-06 14:22 ` [PATCH 4/4] arm64: dts: qcom: milos: Add LPASS LPI pinctrl node Luca Weiss
2026-03-10 11:29 ` Linus Walleij
2026-03-10 12:28 ` Konrad Dybcio
2026-03-24 1:56 ` Bjorn Andersson [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=177431737466.23057.7104535276234811171.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®