From: Andi Shyti <andi.shyti@kernel.org>
To: Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: Robert Foss <rfoss@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Luca Weiss <luca@lucaweiss.eu>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, vladimir.zapolskiy@linaro.org,
konradybcio@kernel.org, stephan.gerhold@linaro.org,
Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v3 0/5] i2c: qcom-cci: Enforce the required CCI clock rate
Date: Fri, 31 Jul 2026 22:54:25 +0200 [thread overview]
Message-ID: <am0LW4Jk_NngWBf8@zenone.zhora.eu> (raw)
In-Reply-To: <20260729-cci-clk-fix-v3-0-f3c731d1596e@oss.qualcomm.com>
> Loic Poulain (5):
> i2c: qcom-cci: Switch msm8953 to the CCI v2 timing/rate config
> i2c: qcom-cci: Support per-mode CCI clock rates
> i2c: qcom-cci: Add 19.2 MHz timings for the v2 CCI
> i2c: qcom-cci: Share the timing table across CCI revisions
> i2c: qcom-cci: Enforce the required CCI clock rate
Can you please rebase the series on top of next/master or
i2c/i2c-next? Patch 2 doesn't apply.
Andi
prev parent reply other threads:[~2026-07-31 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 12:25 [PATCH v3 0/5] i2c: qcom-cci: Enforce the required CCI clock rate Loic Poulain
2026-07-29 12:25 ` [PATCH v3 1/5] i2c: qcom-cci: Switch msm8953 to the CCI v2 timing/rate config Loic Poulain
2026-07-31 14:06 ` Konrad Dybcio
2026-07-31 14:25 ` Loic Poulain
2026-08-03 2:28 ` Wenmeng Liu
2026-07-29 12:25 ` [PATCH v3 2/5] i2c: qcom-cci: Support per-mode CCI clock rates Loic Poulain
2026-07-29 12:25 ` [PATCH v3 3/5] i2c: qcom-cci: Add 19.2 MHz timings for the v2 CCI Loic Poulain
2026-07-29 12:25 ` [PATCH v3 4/5] i2c: qcom-cci: Share the timing table across CCI revisions Loic Poulain
2026-07-29 12:25 ` [PATCH v3 5/5] i2c: qcom-cci: Enforce the required CCI clock rate Loic Poulain
2026-07-31 20:55 ` Andi Shyti
2026-08-01 7:14 ` Loic Poulain
2026-07-31 20:54 ` Andi Shyti [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=am0LW4Jk_NngWBf8@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=luca@lucaweiss.eu \
--cc=rfoss@kernel.org \
--cc=stephan.gerhold@linaro.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=wenmeng.liu@oss.qualcomm.com \
--cc=wsa+renesas@sang-engineering.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