From: Subbaraman Narayanamurthy <quic_subbaram@quicinc.com>
To: Vinod Koul <vkoul@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
David Collins <quic_collinsd@quicinc.com>
Cc: <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
David Dai <daidavid1@codeaurora.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] dt-bindings: spmi: convert Qualcomm SPMI PMIC ARB to dtschema
Date: Mon, 31 Jan 2022 15:02:07 -0800 [thread overview]
Message-ID: <ec54ccc7-ae27-f19c-bb4c-db3d207f4182@quicinc.com> (raw)
In-Reply-To: <20220131172450.2528065-2-vkoul@kernel.org>
On 1/31/22 9:24 AM, Vinod Koul wrote:
> Convert Qualcomm SPMI PMIC arb binding to dtschema format.
No concerns but, there are many patches going around for this.
Fenglin Wu had it in his v4 series [1] which he had dropped in his v5
series [2] as this one [3] from David H got a "Reviewed-by".
So, wondering if this can be dropped off?
[1] https://lore.kernel.org/linux-arm-msm/1640071211-31462-12-git-send-email-quic_fenglinw@quicinc.com/
[2] https://lore.kernel.org/linux-arm-msm/1643178713-17178-1-git-send-email-quic_fenglinw@quicinc.com/
[3] https://lore.kernel.org/linux-arm-msm/20211227170151.73116-1-david@ixit.cz/
-Subbaraman
next prev parent reply other threads:[~2022-01-31 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 17:24 [PATCH 0/3] spmi: pmic-arb: Add support for PMIC v7 and yamlify binding Vinod Koul
2022-01-31 17:24 ` [PATCH 1/3] dt-bindings: spmi: convert Qualcomm SPMI PMIC ARB to dtschema Vinod Koul
2022-01-31 23:02 ` Subbaraman Narayanamurthy [this message]
2022-02-01 5:53 ` Vinod Koul
2022-02-01 15:33 ` Rob Herring
2022-01-31 17:24 ` [PATCH 2/3] dt-bindings: spmi: Add qcom,bus-id Vinod Koul
2022-01-31 17:24 ` [PATCH 3/3] spmi: pmic-arb: Add support for PMIC v7 Vinod Koul
2022-01-31 23:04 ` Subbaraman Narayanamurthy
2022-02-01 5:54 ` Vinod Koul
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=ec54ccc7-ae27-f19c-bb4c-db3d207f4182@quicinc.com \
--to=quic_subbaram@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_collinsd@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).