From: Guenter Roeck <linux@roeck-us.net>
To: Nishanth Menon <nm@ti.com>
Cc: Eduardo Valentin <edubezval@gmail.com>,
Jean Delvare <jdelvare@suse.de>,
lm-sensors@lm-sensors.org, lkml <linux-kernel@vger.kernel.org>,
dt list <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH V2] (gpio-fan): Add thermal control hooks
Date: Tue, 03 Mar 2015 09:32:32 -0800 [thread overview]
Message-ID: <54F5F030.3020200@roeck-us.net> (raw)
In-Reply-To: <54F5EAC8.6040909@ti.com>
On 03/03/2015 09:09 AM, Nishanth Menon wrote:
> On 02/24/2015 02:06 PM, Nishanth Menon wrote:
>> On Tue, Feb 24, 2015 at 1:55 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>>> On Tue, Feb 24, 2015 at 03:29:35PM -0400, Eduardo Valentin wrote:
>>>> Guenter,
>>>>
>>>> On Thu, Jan 08, 2015 at 08:48:40PM -0800, Guenter Roeck wrote:
>>>>> On 01/08/2015 10:05 AM, Nishanth Menon wrote:
>>>>>> Allow gpio-fan to be used as thermal cooling device for platforms that
>>>>>> use GPIO maps to control fans.
>>>>>>
>>>>>> As part of this change, we make the shutdown and remove logic the same
>>>>>> as well.
>>>>>>
>>>>>> Signed-off-by: Nishanth Menon <nm@ti.com>
>>>>>> ---
>>>>>
>>>>> Applied to -next.
>>>>
>>>> What is the target kernel version for this change? It didn't make
>>>> 4.0-rc1
>>>>
>>> If I recall correctly, I had to pull it because the thermal framework
>>> does not provide hooks if disabled. Weird, I am sure I sent an e-mail
>>> about this, but I don't find it right now.
>>>
>>> It can't make it in before the hooks are in place, or we'll need
>>> another version with ifdefs around the thermal registration code.
>>
>> I had posted the required hooks.
>> https://patchwork.kernel.org/patch/5828261/ -> I think Eduardo picked
>> this one up.. So once it hits mainline, we should ideally be clear.
>>
> merged as 12ca7188468ee29c4e717f73db4bf43c90954fc7 upstream. Can we
> pick up this patch now?
>
Done, currently testing. Should make its way into -next in a couple of days
unless there are unexpected problems.
Guenter
next prev parent reply other threads:[~2015-03-03 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 18:05 [PATCH V2] (gpio-fan): Add thermal control hooks Nishanth Menon
2015-01-09 4:48 ` Guenter Roeck
2015-02-24 19:29 ` Eduardo Valentin
2015-02-24 19:55 ` Guenter Roeck
2015-02-24 19:57 ` Eduardo Valentin
2015-02-24 20:06 ` Nishanth Menon
2015-03-03 17:09 ` Nishanth Menon
2015-03-03 17:32 ` Guenter Roeck [this message]
[not found] ` <1420740303-12529-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2015-01-09 11:46 ` Eduardo Valentin
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=54F5F030.3020200@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=nm@ti.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 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).