From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stanislav Zaikin <zstaseg@gmail.com>
Cc: 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>,
Sebastian Reichel <sre@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible
Date: Thu, 17 Sep 2026 12:07:11 +0200 [thread overview]
Message-ID: <20260917-sticky-sheep-from-pluto-adf65b@quoll> (raw)
In-Reply-To: <20260915084901.56622-2-zstaseg@gmail.com>
On Tue, Sep 15, 2026 at 10:48:59AM +0200, Stanislav Zaikin wrote:
> Add the compatible string used by Xiaomi 12 Lite 5G (taoyao) so its
> battery manager can be matched to a device-specific variant in
> qcom_battmgr.
Previously you were asked if the device is compatible with qcm6490. You
responded about something completely else - that you need qcm6490. That
was not the question if you need it or not. The question was are they
compatible and you have entire commit msg to explain that.
Instead, describing standard Linux device driver matching in commit msg
is redundant.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-17 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:48 [PATCH v4 0/3] Add Xiaomi 12 Lite 5G (taoyao) battery support Stanislav Zaikin
2026-09-15 8:48 ` [PATCH v4 1/3] dt-bindings: soc: qcom: add xiaomi,taoyao-pmic-glink compatible Stanislav Zaikin
2026-09-17 10:07 ` Krzysztof Kozlowski [this message]
2026-09-15 8:49 ` [PATCH v4 2/3] power: supply: qcom_battmgr: add Xiaomi taoyao support Stanislav Zaikin
2026-09-15 8:49 ` [PATCH v4 3/3] arm64: dts: qcom: sm7325-xiaomi-taoyao: switch to device-specific pmic-glink compatible Stanislav Zaikin
2026-09-17 11:31 ` Konrad Dybcio
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=20260917-sticky-sheep-from-pluto-adf65b@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=zstaseg@gmail.com \
/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®