From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Vladimir Zapolskiy <vz@kernel.org>
Cc: Loic Poulain <loic.poulain@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: i2c: qcom-cci: Document SM8350 compatible
Date: Sat, 7 Nov 2026 16:27:03 +0200 [thread overview]
Message-ID: <au81MnlqSXPnrttt@shikoro> (raw)
In-Reply-To: <20261104230529.3040285-2-vz@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
On Thu, Nov 05, 2026 at 01:05:27AM +0200, Vladimir Zapolskiy wrote:
> Add Qualcomm SM8350 SoC compatible to the CCI device tree bindings,
> SM8350 CCI is compatible with CCI v2 found on MSM8996.
>
> Signed-off-by: Vladimir Zapolskiy <vz@kernel.org>
> Reviewed-by: Loic Poulain <loic.poulain@oss.qualcomm.com>
Probably qcom tree here as well...
Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-11-07 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 23:05 [PATCH 0/3] arm64: dts: qcom: sm8350: Add CCI and camera MCLK pins Vladimir Zapolskiy
2026-11-04 23:05 ` [PATCH 1/3] dt-bindings: i2c: qcom-cci: Document SM8350 compatible Vladimir Zapolskiy
2026-11-05 8:38 ` Loic Poulain
2026-11-07 14:27 ` Wolfram Sang [this message]
2026-11-04 23:05 ` [PATCH 2/3] arm64: dts: qcom: sm8350: Add CCI device tree nodes Vladimir Zapolskiy
2026-11-05 8:37 ` Loic Poulain
2026-11-07 18:12 ` Vladimir Zapolskiy
2026-11-09 8:46 ` Loic Poulain
2026-11-04 23:05 ` [PATCH 3/3] arm64: dts: qcom: sm8350: Add camera MCLK pinctrl states Vladimir Zapolskiy
2026-11-05 8:56 ` 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=au81MnlqSXPnrttt@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@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-i2c@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=vz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.