From: Krzysztof Kozlowski <krzk@kernel.org>
To: esteuwu@proton.me, Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Support for pmic-glink in SM8475
Date: Fri, 31 Jul 2026 12:00:56 +0200 [thread overview]
Message-ID: <670ca697-40c5-403f-839d-b9470cd0879b@kernel.org> (raw)
In-Reply-To: <20260731-sm8475-pmic-glink-v2-0-28c04928ef22@proton.me>
On 31/07/2026 07:00, Esteban Urrutia via B4 Relay wrote:
> This series adds a compatible string for SM8475 for supporting
> pmic-glink.
> This way, confusion is avoided, because SM8475 takes most
> (CPU/GPU/reserved-memory/etc.) things from SM8450 and some (PHY/eUSB)
> from SM8550.
> Instead of using one or the other, add a different compatible string.
>
> Signed-off-by: Esteban Urrutia <esteuwu@proton.me>
> ---
> Changes in v2:
> - Apply suggestions from Krzysztof
Which ones? I did not see any improvements. This has to be specific.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-07-31 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 5:00 [PATCH v2 0/2] Support for pmic-glink in SM8475 Esteban Urrutia via B4 Relay
2026-07-31 5:00 ` [PATCH v2 1/2] dt-bindings: soc: qcom: qcom,pmic-glink: Add compatible string for SM8475 Esteban Urrutia via B4 Relay
2026-07-31 9:58 ` Krzysztof Kozlowski
2026-07-31 14:44 ` Esteban Urrutia
2026-07-31 15:30 ` Konrad Dybcio
2026-07-31 5:00 ` [PATCH v2 2/2] usb: typec: ucsi: ucsi_glink: " Esteban Urrutia via B4 Relay
2026-07-31 5:40 ` Esteban Urrutia
2026-07-31 9:59 ` Krzysztof Kozlowski
2026-07-31 14:48 ` Esteban Urrutia
2026-07-31 10:00 ` Krzysztof Kozlowski [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=670ca697-40c5-403f-839d-b9470cd0879b@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=esteuwu@proton.me \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@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