From: "Nayak, Rajendra" <rnayak@codeaurora.org>
To: Eduardo Valentin <edubezval@gmail.com>
Cc: andy.gross@linaro.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
rui.zhang@intel.com, sboyd@codeaurora.org, nrajan@codeaurora.org,
lina.iyer@linaro.org, punit.agrawal@arm.com,
srinivas.kandagatla@linaro.org
Subject: Re: [PATCH v5 00/11] qcom: Add support for TSENS driver
Date: Thu, 21 Apr 2016 16:19:34 +0530 [thread overview]
Message-ID: <5718B03E.8040500@codeaurora.org> (raw)
In-Reply-To: <20160420235127.GC2558@localhost.localdomain>
Hi Eduardo,
On 4/21/2016 5:21 AM, Eduardo Valentin wrote:
> On Thu, Apr 14, 2016 at 03:01:48PM +0530, Rajendra Nayak wrote:
>> Current set of patches apply on 4.6-rc3. nvmem apis are currently
>> broken and hence need to pull in the fixes for it as proposed here [1]
>
>
> Could you please clarify this a bit?
>
> Do I understand properly that we need to wait until [1] gets merged to
> get the driver functional again after applying this series?
Yes, thats correct. We need the nvmem apis to be functional for this
series to work.
I have added Srini who is working on fixing it and reworking [1] as
Mark wasn't happy with the current approach.
regards,
Rajendra
next prev parent reply other threads:[~2016-04-21 10:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 9:31 [PATCH v5 00/11] qcom: Add support for TSENS driver Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 01/11] thermal: qcom: tsens: Add a skeletal TSENS drivers Rajendra Nayak
2016-04-28 0:20 ` Eduardo Valentin
2016-05-05 4:50 ` Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 02/11] thermal: qcom: tsens-8916: Add support for 8916 family of SoCs Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 03/11] thermal: qcom: tsens-8974: Add support for 8974 " Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 04/11] thermal: core: export apis to get slope and offset Rajendra Nayak
2016-04-28 0:08 ` Eduardo Valentin
2016-05-05 4:47 ` Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 05/11] thermal: qcom: tsens-8960: Add support for 8960 family of SoCs Rajendra Nayak
2016-04-28 0:10 ` Eduardo Valentin
2016-05-05 4:48 ` Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 06/11] thermal: qcom: tsens-8996: Add support for 8996 " Rajendra Nayak
2016-04-28 0:13 ` Eduardo Valentin
2016-04-14 9:31 ` [PATCH v5 07/11] arm: dts: msm8974: Add thermal zones, tsens and qfprom nodes Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 08/11] arm: dts: apq8064: " Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 09/11] arm: dts: apq8084: " Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 10/11] arm64: dts: msm8916: " Rajendra Nayak
2016-04-14 9:31 ` [PATCH v5 11/11] arm64: dts: msm8996: " Rajendra Nayak
2016-04-28 0:03 ` Eduardo Valentin
2016-05-05 4:47 ` Rajendra Nayak
2016-04-20 23:51 ` [PATCH v5 00/11] qcom: Add support for TSENS driver Eduardo Valentin
2016-04-21 10:49 ` Nayak, Rajendra [this message]
2016-04-22 9:07 ` Srinivas Kandagatla
2016-04-28 0:03 ` Eduardo Valentin
2016-05-05 4:46 ` Rajendra Nayak
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=5718B03E.8040500@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=edubezval@gmail.com \
--cc=lina.iyer@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nrajan@codeaurora.org \
--cc=punit.agrawal@arm.com \
--cc=rui.zhang@intel.com \
--cc=sboyd@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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).