From: Thara Gopinath <thara.gopinath@linaro.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: rui.zhang@intel.com, daniel.lezcano@linaro.org,
davem@davemloft.net, kuba@kernel.org, luciano.coelho@intel.com,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-pm@vger.kernel.org,
amitk@kernel.org, nathan.errera@intel.com
Subject: Re: [PATCH 1/2] net: wireless: intel: iwlwifi: mvm: tt: Replace thermal_notify_framework
Date: Wed, 20 Jan 2021 05:46:08 -0500 [thread overview]
Message-ID: <9452ceb2-3e3c-399b-4cfd-a31f71200fa3@linaro.org> (raw)
In-Reply-To: <87pn20garq.fsf@codeaurora.org>
On 1/19/21 11:19 AM, Kalle Valo wrote:
> Thara Gopinath <thara.gopinath@linaro.org> writes:
>
>> thermal_notify_framework just updates for a single trip point where as
>> thermal_zone_device_update does other bookkeeping like updating the
>> temperature of the thermal zone and setting the next trip point etc.
>> Replace thermal_notify_framework with thermal_zone_device_update as the
>> later is more thorough.
>>
>> Signed-off-by: Thara Gopinath <thara.gopinath@linaro.org>
>
> The title could be just "iwlwifi: mvm: tt: Replace
> thermal_notify_framework".
>
> But via which tree is this going? I assume it's not
> wireless-drivers-next so:
Thanks for the quick review. I would say thermal.
I will fix the subject and add your acked in the next version.
>
> Acked-by: Kalle Valo <kvalo@codeaurora.org> >
>
--
Warm Regards
Thara
next prev parent reply other threads:[~2021-01-20 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 14:05 [PATCH 0/2] thermal: Replace thermal_notify_framework with thermal_zone_device_update Thara Gopinath
2021-01-19 14:05 ` [PATCH 1/2] net: wireless: intel: iwlwifi: mvm: tt: Replace thermal_notify_framework Thara Gopinath
2021-01-19 16:19 ` Kalle Valo
2021-01-20 10:46 ` Thara Gopinath [this message]
2021-01-19 14:05 ` [PATCH 2/2] drivers: thermal: Remove thermal_notify_framework Thara Gopinath
2021-01-20 2:56 ` [PATCH 0/2] thermal: Replace thermal_notify_framework with thermal_zone_device_update Zhang, Rui
2021-01-20 10:53 ` Thara Gopinath
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=9452ceb2-3e3c-399b-4cfd-a31f71200fa3@linaro.org \
--to=thara.gopinath@linaro.org \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=nathan.errera@intel.com \
--cc=netdev@vger.kernel.org \
--cc=rui.zhang@intel.com \
/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.