From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Doug Anderson <dianders@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>
Cc: mturney@codeaurora.org, Jeffrey Hugo <jhugo@codeaurora.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
dhavalp@codeaurora.org,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
sparate@codeaurora.org,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
mkurumel@codeaurora.org, Ravi Kumar Bokka <rbokka@codeaurora.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 3/4] nvmem: qfprom: Add fuse blowing support
Date: Tue, 7 Jul 2020 15:54:44 +0100 [thread overview]
Message-ID: <bf75ef0d-1267-377e-9875-e44be3f5e406@linaro.org> (raw)
In-Reply-To: <CAD=FV=UJ9fm0z-6kAm4wDCfb8Ugr53i4RciCHTJT91ec27Mm4A@mail.gmail.com>
On 07/07/2020 15:52, Doug Anderson wrote:
>
> Given that I've resolved previous feedback, I've been assuming that
> the series looks fine and we're sitting waiting for Rob Herring's
> blessings on the bindings before landing. Is that correct?
That's correct!
--srini
next prev parent reply other threads:[~2020-07-07 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 14:49 [PATCH v4 0/4] nvmem: qfprom: Patches for fuse blowing on Qualcomm SoCs Douglas Anderson
2020-06-22 14:49 ` [PATCH v4 1/4] dt-bindings: nvmem: qfprom: Convert to yaml Douglas Anderson
2020-07-09 23:16 ` Rob Herring
2020-06-22 14:49 ` [PATCH v4 2/4] dt-bindings: nvmem: Add properties needed for blowing fuses Douglas Anderson
2020-07-09 23:16 ` Rob Herring
2020-06-22 14:49 ` [PATCH v4 3/4] nvmem: qfprom: Add fuse blowing support Douglas Anderson
2020-07-01 15:09 ` Ravi Kumar Bokka (Temp)
2020-07-01 15:13 ` Doug Anderson
2020-07-07 14:52 ` Doug Anderson
2020-07-07 14:54 ` Srinivas Kandagatla [this message]
2020-06-22 14:49 ` [PATCH v4 4/4] arm64: dts: qcom: sc7180: Add properties to qfprom for fuse blowing Douglas Anderson
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=bf75ef0d-1267-377e-9875-e44be3f5e406@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dhavalp@codeaurora.org \
--cc=dianders@chromium.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkurumel@codeaurora.org \
--cc=mturney@codeaurora.org \
--cc=rbokka@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=sparate@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.