From: Oleg Keri <okerixx@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Guru Das Srinagesh <linux@gurudas.dev>,
linux-arm-msm@vger.kernel.org, mfd@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mfd: qcom-pm8008: support PMICs with no interrupt line
Date: Tue, 22 Sep 2026 13:00:06 +0200 [thread overview]
Message-ID: <179007480602.173050.17097175603597060097@gmail.com> (raw)
In-Reply-To: <20260922101459.GB2730113@google.com>
Hi Lee,
On Tue, Sep 22, 2026, Lee Jones wrote:
> What on earth is going on here:
>
> https://lore.kernel.org/r/20260907-glymur_camss-v2-5-75f7982dc983@oss.qualcomm.com
Three postings for the same PMIC, in order:
- Nihal's Glymur CAMSS v2 (7 Sep) carried PM8010 support for qcom-pm8008
as patches 3-6, including the no-interrupt case.
- My series (8 Sep) was a strict subset of that, written without
checking the list first. I withdrew it the same day on the cover
letter [1]; please drop it.
- Nihal dropped the PMIC patches from his v3 (17 Sep), and Jishnu posted
them as a dedicated series, "mfd: qcom-pm8008: Add support for PM8010
over I2C" (18 Sep) [2]. That is the one to review. It runs on my
board, PM8010 with no interrupt line, and I sent a Tested-by there.
[1] https://lore.kernel.org/all/178887481187.4612.2819576206036967152@gmail.com/
[2] https://lore.kernel.org/all/20260918-pm8010_i2c_support-v1-0-de33d78fad9d@oss.qualcomm.com/
Sorry for the confusion,
Oleg
next prev parent reply other threads:[~2026-09-22 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 13:07 [PATCH 0/2] mfd: qcom-pm8008: support PMICs with no interrupt line Oleg Keri
2026-09-08 13:07 ` [PATCH 1/2] dt-bindings: mfd: qcom,pm8008: make the interrupt line optional Oleg Keri
2026-09-08 13:22 ` sashiko-bot
2026-09-08 13:07 ` [PATCH 2/2] mfd: qcom-pm8008: support PMICs with no interrupt line Oleg Keri
2026-09-08 13:15 ` sashiko-bot
2026-09-22 10:14 ` Lee Jones
2026-09-22 11:00 ` Oleg Keri [this message]
2026-09-08 13:40 ` [PATCH 0/2] " Oleg Keri
2026-09-10 9:10 ` Jishnu Prakash
2026-09-10 9:19 ` Konrad Dybcio
2026-09-10 12:44 ` Oleg Keri
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=179007480602.173050.17097175603597060097@gmail.com \
--to=okerixx@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@gurudas.dev \
--cc=mfd@lists.linux.dev \
--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