From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Ravi Kumar Bokka <rbokka@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
rnayak@codeaurora.org, saiprakash.ranjan@codeaurora.org,
dhavalp@codeaurora.org, mturney@codeaurora.org,
sparate@codeaurora.org, c_rbokka@codeaurora.org,
mkurumel@codeaurora.org
Subject: Re: [RFC v2 2/3] drivers: nvmem: Add QTI qfprom-efuse support
Date: Mon, 15 Jun 2020 10:56:55 +0100 [thread overview]
Message-ID: <39ad93ee-236d-0e5e-571a-28ef91173309@linaro.org> (raw)
In-Reply-To: <1591868882-16553-3-git-send-email-rbokka@codeaurora.org>
I think Doug already covered most of the comments and his fixes seems be
in right direction.
On 11/06/2020 10:48, Ravi Kumar Bokka wrote:
> + qfpraw = platform_get_resource_byname(pdev, IORESOURCE_MEM, "raw");
> +
> + priv->qfpraw = devm_ioremap_resource(dev, qfpraw);
> + if (IS_ERR(priv->qfpraw)) {
General comment for up-streaming is that your patch should not break
whats in mainline, Your patch is totally ignoring!! Please be mindful
while doing changes to drivers which are used by other platforms.
--srini
> + ret = PTR_ERR(priv->qfpraw);
> + goto err;
> + }
> +
> + qfpconf = platform_get_resource_byname(pdev, IORESOURCE_MEM, "conf");
> +
> + priv->qfpconf = devm_ioremap_resource(dev, qfpconf);
> + if (IS_ERR(priv->qfpconf)) {
> + ret = PTR_ERR(priv->qfpconf);
> + goto err;
> + }
> +
> + qfpcorrected = platform_get_resource_byname(pdev, IORESOURCE_MEM,
> + "corrected");
> +
> + priv->qfpcorrected = devm_ioremap_resource(dev, qfpcorrected);
> + if (IS_ERR(priv->qfpcorrected)) {
> + ret = PTR_ERR(priv->qfpcorrected);
> + goto err;
> + }
next prev parent reply other threads:[~2020-06-15 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:47 [RFC v2 0/3] Add QTI QFPROM-Efuse driver support Ravi Kumar Bokka
2020-06-11 9:48 ` [RFC v2 1/3] dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse Ravi Kumar Bokka
2020-06-11 12:18 ` Rajendra Nayak
2020-06-12 21:58 ` Rob Herring
2020-06-12 21:59 ` Doug Anderson
2020-06-12 23:15 ` Doug Anderson
2020-06-15 10:44 ` Srinivas Kandagatla
2020-06-15 14:17 ` Rob Herring
2020-06-15 14:27 ` Doug Anderson
2020-06-15 14:28 ` Srinivas Kandagatla
2020-06-11 9:48 ` [RFC v2 2/3] drivers: nvmem: Add QTI qfprom-efuse support Ravi Kumar Bokka
2020-06-13 20:33 ` Doug Anderson
2020-06-15 10:44 ` Srinivas Kandagatla
2020-06-15 17:13 ` Doug Anderson
2020-06-17 14:54 ` Doug Anderson
2020-06-15 9:56 ` Srinivas Kandagatla [this message]
2020-06-11 9:48 ` [RFC v2 3/3] arm64: dts: qcom: sc7180: Add qfprom-efuse Ravi Kumar Bokka
2020-06-13 20:23 ` Doug 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=39ad93ee-236d-0e5e-571a-28ef91173309@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=c_rbokka@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dhavalp@codeaurora.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 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).