From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, linux-pm@vger.kernel.org,
stable@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>,
Eduardo Valentin <edubezval@gmail.com>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: [PATCH] thermal: exynos: Propagate error value from tmu_read()
Date: Tue, 27 Feb 2018 16:25:02 +0100 [thread overview]
Message-ID: <1635777.KPLQ7M4AcC@amdc3058> (raw)
In-Reply-To: <20180227151405.9618-1-m.szyprowski@samsung.com>
On Tuesday, February 27, 2018 04:14:05 PM Marek Szyprowski wrote:
> tmu_read() in case of Exynos4210 might return error for out of bound
> values. Current code ignores such value, what leads to reporting critical
> temperature value. Add proper error code propagation to exynos_get_temp()
> function.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> CC: stable@vger.kernel.org # v4.6+
Thanks for fixing this.
Acked-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> ---
> This patch is prepared on top of "thermal: exynos: Reading temperature
> makes sense only when TMU is turned on" patch. Both are required
> to finally fix thermal support on Exynos4210 based boards.
>
> This patch only applies cleanly together with the mentioned "thermal:
> exynos: Reading temperature makes sense only when TMU is turned on"
> patch on v4.6+ kernels.
You may also add:
Fixes: 3b6a1a805f34 ("thermal: samsung: core: Exynos TMU rework to use device tree for configuration")
to the patch description.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2018-02-27 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180227151408eucas1p20dc5f0974dda96b4ebaff7948eda766a@eucas1p2.samsung.com>
2018-02-27 15:14 ` [PATCH] thermal: exynos: Propagate error value from tmu_read() Marek Szyprowski
2018-02-27 15:25 ` Bartlomiej Zolnierkiewicz [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=1635777.KPLQ7M4AcC@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=edubezval@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rui.zhang@intel.com \
--cc=stable@vger.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