From: Esteban Urrutia <esteuwu@proton.me>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] pinctrl: qcom: Add SM8475 pinctrl driver
Date: Thu, 20 Aug 2026 00:55:38 +0000 [thread overview]
Message-ID: <912a1eea-285e-4b61-8173-8878948828ce@proton.me> (raw)
In-Reply-To: <befb87e4-3b29-4e97-be6d-7dcc5e826dbe@oss.qualcomm.com>
On 8/19/26 7:39 AM, Konrad Dybcio wrote:
> This is a whole new driver to accomodate a single change (removing
> function3 - pll_clk_aux from pin 98). I would just add a comment
> somewhere and not bother, especially since IIUC this is a debug
> mux output that doesn't get used in practice
Ack
Regards,
Esteban
prev parent reply other threads:[~2026-08-20 0:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 7:30 [PATCH v2 0/4] Pinctrl support for SM8475 Esteban Urrutia via B4 Relay
2026-08-02 7:30 ` [PATCH v2 1/4] pinctrl: qcom: sm8450: Remove duplicate reference to gpio81 Esteban Urrutia via B4 Relay
2026-08-10 11:24 ` Bartosz Golaszewski
2026-08-10 16:01 ` Esteban Urrutia
2026-08-12 8:15 ` Bartosz Golaszewski
2026-08-12 18:25 ` Esteban Urrutia
2026-08-02 7:30 ` [PATCH v2 2/4] pinctrl: qcom: Commonize pinctrl-sm8450 headers Esteban Urrutia via B4 Relay
2026-08-02 7:44 ` sashiko-bot
2026-08-02 7:30 ` [PATCH v2 3/4] dt-bindings: pinctrl: qcom,sm8450-tlmm: Add compatible for SM8475 Esteban Urrutia via B4 Relay
2026-08-02 7:40 ` sashiko-bot
2026-08-03 10:00 ` Krzysztof Kozlowski
2026-08-07 2:17 ` Esteban Urrutia
2026-08-02 7:30 ` [PATCH v2 4/4] pinctrl: qcom: Add SM8475 pinctrl driver Esteban Urrutia via B4 Relay
2026-08-19 11:39 ` Konrad Dybcio
2026-08-20 0:55 ` Esteban Urrutia [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=912a1eea-285e-4b61-8173-8878948828ce@proton.me \
--to=esteuwu@proton.me \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--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=phone-devel@vger.kernel.org \
--cc=robh@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