From: Zhang Rui <rui.zhang@intel.com>
To: Ilkka Koskinen <ilkka.koskinen@linux.intel.com>
Cc: linux-pm@vger.kernel.org, edubezval@gmail.com,
jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH 1/2] Thermal/int340x: Clear the error value of the last acpi_bus_get_device() call
Date: Tue, 09 Dec 2014 11:48:50 +0800 [thread overview]
Message-ID: <1418096930.12435.5.camel@rzhang1-toshiba> (raw)
In-Reply-To: <1418090492-87508-2-git-send-email-ilkka.koskinen@linux.intel.com>
On Mon, 2014-12-08 at 18:01 -0800, Ilkka Koskinen wrote:
> Previously the return value of the last acpi_bus_get_device() was
> returned. However, since we only report those issues, it should be
> cleared to continue as expected.
>
> Signed-off-by: Ilkka Koskinen <ilkka.koskinen@linux.intel.com>
> Acked-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
applied.
thanks,
rui
> ---
> drivers/thermal/int340x_thermal/acpi_thermal_rel.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/thermal/int340x_thermal/acpi_thermal_rel.c b/drivers/thermal/int340x_thermal/acpi_thermal_rel.c
> index ac5c405..e4e61b3 100644
> --- a/drivers/thermal/int340x_thermal/acpi_thermal_rel.c
> +++ b/drivers/thermal/int340x_thermal/acpi_thermal_rel.c
> @@ -131,6 +131,8 @@ int acpi_parse_trt(acpi_handle handle, int *trt_count, struct trt **trtp,
> pr_warn("Failed to get target ACPI device\n");
> }
>
> + result = 0;
> +
> *trtp = trts;
> /* don't count bad entries */
> *trt_count -= nr_bad_entries;
next prev parent reply other threads:[~2014-12-09 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 2:01 [PATCH 0/2] Thermal/int340x: _art and _trt fixes Ilkka Koskinen
2014-12-09 2:01 ` [PATCH 1/2] Thermal/int340x: Clear the error value of the last acpi_bus_get_device() call Ilkka Koskinen
2014-12-09 3:48 ` Zhang Rui [this message]
2014-12-09 2:01 ` [PATCH 2/2] Thermal/int340x: Handle properly the case when _trt or _art acpi entry is missing Ilkka Koskinen
2014-12-09 3:48 ` Zhang Rui
2014-12-09 20:26 ` Ilkka Koskinen
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=1418096930.12435.5.camel@rzhang1-toshiba \
--to=rui.zhang@intel.com \
--cc=edubezval@gmail.com \
--cc=ilkka.koskinen@linux.intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-pm@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 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.