From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Melody Olvera <quic_molvera@quicinc.com>,
Vinod Koul <vkoul@kernel.org>, Stephen Boyd <sboyd@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 0/2] spmi: pmic-arb: Add support for PMIC v7
Date: Sun, 20 Nov 2022 11:48:49 +0100 [thread overview]
Message-ID: <90ca85c1-a5ed-3762-31dc-45f665e0762b@linaro.org> (raw)
In-Reply-To: <f6842c89-fffc-e1b0-c68f-287111974378@quicinc.com>
On 18/11/2022 20:24, Melody Olvera wrote:
>
>
> On 11/3/2022 9:27 AM, Vinod Koul wrote:
>> On 14-09-22, 22:22, Vinod Koul wrote:
>>> Hello,
>>>
>>> The is version 5 of support for PMIC v7. I have added a new property
>>> qcom,bus-id for supporting v7 and then add driver changes for v7
>> Stephen,
>>
>> Can you pick this? It has been so long...
>
> Hi Stephen,
>
> Do you mind looking at this? I've got some patches that depend on functionality here...
> https://lore.kernel.org/all/20221118192241.29384-1-quic_molvera@quicinc.com/
This was merged.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-11-20 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 16:52 [PATCH v5 0/2] spmi: pmic-arb: Add support for PMIC v7 Vinod Koul
2022-09-14 16:52 ` [PATCH v5 1/2] dt-bindings: spmi: Add qcom,bus-id Vinod Koul
2022-09-15 9:51 ` Krzysztof Kozlowski
2022-09-15 11:59 ` Rob Herring
2022-09-16 4:40 ` Vinod Koul
2022-09-16 18:30 ` Bjorn Andersson
2022-09-21 15:15 ` [PATCH v5 0/2] spmi: pmic-arb: Add support for PMIC v7 Vinod Koul
2022-10-03 5:57 ` Vinod Koul
2022-11-03 14:27 ` Vinod Koul
2022-11-18 19:24 ` Melody Olvera
2022-11-20 10:48 ` Krzysztof Kozlowski [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=90ca85c1-a5ed-3762-31dc-45f665e0762b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_molvera@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).