Linux I2C development
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Birk Skyum <birk.skyum@pm.me>, Andi Shyti <andi.shyti@kernel.org>,
	Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>,
	Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>
Cc: Sasha Levin <sashal@kernel.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	Daniel J Blueman <daniel@quora.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Manikanta Mylavarapu <quic_mmanikan@quicinc.com>,
	linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH] Revert "i2c: qcom-geni: Fix hardcoded clock index in SE_GENI_CLK_SEL"
Date: Wed, 14 Oct 2026 18:33:23 -0400	[thread overview]
Message-ID: <20261014213019.rc-reply-0002@kernel.org> (raw)
In-Reply-To: <20261014130805.48840-1-birk.skyum@pm.me>

On Wed, Oct 14, 2026 at 01:08:08PM +0000, Birk Skyum wrote:
> This reverts commit cb97bf3d4f91453b881acaf8e9f0cc47bb40b604.

Thanks for the report and the bisection. I've dropped the backport of
cb97bf3d4f91 ("i2c: qcom-geni: Fix hardcoded clock index in SE_GENI_CLK_SEL")
from the pending 6.6, 6.1, 5.15 and 5.10 queues.

7.2.y and 6.18.y will pick up the mainline revert or fix once it lands in
Linus's tree.

-- 
Thanks,
Sasha

      parent reply	other threads:[~2026-10-14 22:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 13:08 [PATCH] Revert "i2c: qcom-geni: Fix hardcoded clock index in SE_GENI_CLK_SEL" Birk Skyum
2026-10-14 13:17 ` Konrad Dybcio
2026-10-14 22:33 ` Sasha Levin [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=20261014213019.rc-reply-0002@kernel.org \
    --to=sashal@kernel.org \
    --cc=andersson@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=birk.skyum@pm.me \
    --cc=daniel@quora.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mukesh.savaliya@oss.qualcomm.com \
    --cc=quic_mmanikan@quicinc.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=viken.dadhaniya@oss.qualcomm.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