From: Eduardo Valentin <edubezval@gmail.com> To: Guenter Roeck <linux@roeck-us.net> Cc: Nishanth Menon <nm@ti.com>, Jean Delvare <jdelvare@suse.de>, lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [PATCH V2] (gpio-fan): Add thermal control hooks Date: Tue, 24 Feb 2015 15:57:51 -0400 [thread overview] Message-ID: <20150224195749.GA559@developer.amazonguestwifi.org> (raw) In-Reply-To: <20150224195457.GA16245@roeck-us.net> [-- Attachment #1: Type: text/plain, Size: 1368 bytes --] On Tue, Feb 24, 2015 at 11:55:23AM -0800, Guenter Roeck 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. Got it! I applied the fix that Nishanth sent to thermal.h [1]. I am planing to send it during 4.0 rc cycles. Thanks for the clarification. [1] - https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-thermal.git/commit/?h=fixes&id=12ca7188468ee29c4e717f73db4bf43c90954fc7 > > Guenter Eduardo Valentin [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eduardo Valentin <edubezval@gmail.com> To: Guenter Roeck <linux@roeck-us.net> Cc: Nishanth Menon <nm@ti.com>, Jean Delvare <jdelvare@suse.de>, lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-pm@vger.kernel.org Subject: Re: [lm-sensors] [PATCH V2] (gpio-fan): Add thermal control hooks Date: Tue, 24 Feb 2015 19:57:51 +0000 [thread overview] Message-ID: <20150224195749.GA559@developer.amazonguestwifi.org> (raw) In-Reply-To: <20150224195457.GA16245@roeck-us.net> [-- Attachment #1.1: Type: text/plain, Size: 1368 bytes --] On Tue, Feb 24, 2015 at 11:55:23AM -0800, Guenter Roeck 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. Got it! I applied the fix that Nishanth sent to thermal.h [1]. I am planing to send it during 4.0 rc cycles. Thanks for the clarification. [1] - https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-thermal.git/commit/?h=fixes&id=12ca7188468ee29c4e717f73db4bf43c90954fc7 > > Guenter Eduardo Valentin [-- Attachment #1.2: Digital signature --] [-- Type: application/pgp-signature, Size: 473 bytes --] [-- Attachment #2: Type: text/plain, Size: 153 bytes --] _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2015-02-24 19:57 UTC|newest] Thread overview: 21+ 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-08 18:05 ` [lm-sensors] " Nishanth Menon 2015-01-08 18:05 ` Nishanth Menon 2015-01-09 4:48 ` Guenter Roeck 2015-01-09 4:48 ` [lm-sensors] " Guenter Roeck 2015-02-24 19:29 ` Eduardo Valentin 2015-02-24 19:29 ` [lm-sensors] " Eduardo Valentin 2015-02-24 19:55 ` Guenter Roeck 2015-02-24 19:55 ` [lm-sensors] " Guenter Roeck 2015-02-24 19:57 ` Eduardo Valentin [this message] 2015-02-24 19:57 ` Eduardo Valentin 2015-02-24 20:06 ` Nishanth Menon 2015-02-24 20:06 ` [lm-sensors] " Nishanth Menon 2015-03-03 17:09 ` Nishanth Menon 2015-03-03 17:09 ` [lm-sensors] " Nishanth Menon 2015-03-03 17:09 ` Nishanth Menon 2015-03-03 17:32 ` Guenter Roeck 2015-03-03 17:32 ` [lm-sensors] " Guenter Roeck 2015-01-09 11:46 ` Eduardo Valentin 2015-01-09 11:46 ` [lm-sensors] " Eduardo Valentin 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=20150224195749.GA559@developer.amazonguestwifi.org \ --to=edubezval@gmail.com \ --cc=devicetree@vger.kernel.org \ --cc=jdelvare@suse.de \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pm@vger.kernel.org \ --cc=linux@roeck-us.net \ --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: linkBe 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.