From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759778AbdKPPVM (ORCPT ); Thu, 16 Nov 2017 10:21:12 -0500 Received: from mail-pf0-f196.google.com ([209.85.192.196]:57035 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759698AbdKPPVC (ORCPT ); Thu, 16 Nov 2017 10:21:02 -0500 X-Google-Smtp-Source: AGs4zMYGFMsuQr28Ces3jOk4AtZejAxQkDkRP9pLK7itEbpmoucUZ1Rkjp0L66peajekiC8vGzt0+g== Date: Thu, 16 Nov 2017 20:50:58 +0530 From: Viresh Kumar To: Ionela Voinescu Cc: Eduardo Valentin , "Rafael J. Wysocki" , Daniel Lezcano , Rafael Wysocki , Amit Daniel Kachhap , Javi Merino , Zhang Rui , Steven Rostedt , Ingo Molnar , Linux PM , Vincent Guittot , lukasz.luba@arm.com, Linux Kernel Mailing List , Javi Merino , Punit Agrawal Subject: Re: [PATCH 4/4] cpu_cooling: Drop static-power related stuff Message-ID: <20171116152058.GR3257@vireshk-i7> References: <761f7963-8b6d-b002-5404-a9ad0acf84d6@linaro.org> <20171115154311.GA3005@localhost.localdomain> <20171115182047.GA4831@localhost.localdomain> <65fef2a1-d23f-3de2-bd91-021296c3e2f7@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <65fef2a1-d23f-3de2-bd91-021296c3e2f7@arm.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16-11-17, 15:02, Ionela Voinescu wrote: > When it was added in lsk 3.18 in what was then a thermal driver for Juno > it was believed to have an effect in thermal mitigation, but that was > not proven later as to justify posting it upstream, and that is why the > code never made it in mainline. > The code added there can be found at: > https://git.linaro.org/landing-teams/working/arm/kernel-release.git/tree/drivers/thermal/scpi-thermal.c?h=lsk-3.18-armlt#n247 > > As for removing this code now, I would not want to make that decision without > spending more time to check if it impacts other customer codelines. > I'll come back with a reply to this in the next couple of days. Sure, we can wait for few days definitely :) -- viresh