From: Zhang Rui <rui.zhang@intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
Eduardo Valentin <edubezval@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: Missing patches for thermal for 5.2
Date: Tue, 07 May 2019 08:24:22 +0800 [thread overview]
Message-ID: <1557188662.5080.1.camel@intel.com> (raw)
In-Reply-To: <b3fbf910-d073-1dd9-649c-eea370ae71f7@linaro.org>
On 一, 2019-05-06 at 15:17 +0200, Daniel Lezcano wrote:
> Hi Eduardo, Zhang,
>
> AFAICS, the following patches are missing for 5.2:
>
>
> [PATCH -next] mlxsw: Remove obsolete dependency on THERMAL=m
>
This one is already in my tree.
https://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git/commit
/?h=next&id=980d43f24d59491aa1c5552171454ac25fb86ea2
And I think the below patches should go through Eduardo' tree.
thanks,
rui
> [PATCH v3 1/3] thermal: rockchip: fix up the tsadc pinctrl setting
> error
>
> [PATCH v3 2/3] dt-bindings: rockchip-thermal: Support the PX30 SoC
> compatible
>
> [PATCH v3 3/3] thermal: rockchip: Support the PX30 SoC in thermal
> driver
>
> [PATCH] thermal: cpu_cooling: Actually trace CPU load in
> thermal_power_cpu_get_power
>
> [PATCH] thermal/drivers/cpu_cooling: Remove pointless test in
> power2state()
>
> [PATCH - resend] thermal/drivers/cpu_cooling: Fixup the header and
> copyright
>
> [PATCH - resend 2/3] thermal/drivers/cpu_cooling: Add Software
> Package
> Data Exchange (SPDX)
>
> [PATCH - resend 3/3] thermal/drivers/cpu_cooling: Remove pointless
> field
>
>
>
> This one is pending:
>
> [PATCH] thermal/drivers/of: Add a get_temp_id callback function
>
> The series [PATCH v3 00/13] QorIQ TMU multi-sensor and HWMON support
> depends on it.
>
> Hope that helps.
>
> -- Daniel
>
>
>
prev parent reply other threads:[~2019-05-07 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 13:17 Missing patches for thermal for 5.2 Daniel Lezcano
2019-05-07 0:24 ` Zhang Rui [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=1557188662.5080.1.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).