Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754313AbdIZEOE (ORCPT ); Tue, 26 Sep 2017 00:14:04 -0400 Received: from mail-oi0-f53.google.com ([209.85.218.53]:55888 "EHLO mail-oi0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754090AbdIZEOC (ORCPT ); Tue, 26 Sep 2017 00:14:02 -0400 X-Google-Smtp-Source: AOwi7QDm+MMkgd4K6ExBoh/giVlQQgSKEefj4IT27KqZhJo9X5vQdOl/Rae8Fa1UqwEq/7PcsObhdA== Subject: Re: [PATCH v4 2/4] thermal: add brcmstb AVS TMON driver To: "Zhang, Rui" , Rafal Milecki Cc: Markus Mayer , Eduardo Valentin , Rob Herring , Mark Rutland , Doug Berger , Brian Norris , Gregory Fong , Russell King , Catalin Marinas , Will Deacon , Arnd Bergmann , Olof Johansson , Broadcom Kernel List , Power Management List , Device Tree List , ARM Kernel List , Linux Kernel Mailing List , Markus Mayer References: <20170809220257.4234-1-code@mmayer.net> <20170809220257.4234-3-code@mmayer.net> <1502777298.2591.1.camel@intel.com> <95da51df3cadbb05f721f2e5b8d59f8d@milecki.pl> <1502779721.2591.4.camel@intel.com> <4ec0715e-fcd7-3aec-3589-96426575c373@gmail.com> <744357E9AAD1214791ACBA4B0B9092636BE1FB55@SHSMSX101.ccr.corp.intel.com> From: Florian Fainelli Message-ID: <1e23383c-7c63-04fc-0f07-21b0e418e3de@gmail.com> Date: Mon, 25 Sep 2017 21:13:57 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <744357E9AAD1214791ACBA4B0B9092636BE1FB55@SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset=UTF-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3198 Lines: 77 On 09/25/2017 08:02 PM, Zhang, Rui wrote: > Hi, Florian, > > This patch set was dropped in the last minute because of this discussion > https://patchwork.kernel.org/patch/9936325/ > as I don’t want to rebase the patch before sending the pull request. Ah, you wanted to squash that patch into the initial submission? > > I don’t think we can make it for 4.14. > Eduardo will be back and pick the soc patches for 4.15. I assume you would want to get that particular patch squashed into a clean submission targeting 4.15 now, right? Thanks > > Thanks, > rui > > > > -----Original Message----- > From: Florian Fainelli [mailto:f.fainelli@gmail.com] > Sent: Monday, September 25, 2017 5:11 AM > To: Zhang, Rui ; Rafał Miłecki > Cc: Markus Mayer ; Eduardo Valentin ; Rob Herring ; Mark Rutland ; Doug Berger ; Brian Norris ; Gregory Fong ; Russell King ; Catalin Marinas ; Will Deacon ; Arnd Bergmann ; Olof Johansson ; Broadcom Kernel List ; Power Management List ; Device Tree List ; ARM Kernel List ; Linux Kernel Mailing List ; Markus Mayer > Subject: Re: [PATCH v4 2/4] thermal: add brcmstb AVS TMON driver > Importance: High > > Le 08/14/17 à 23:48, Zhang Rui a écrit : >> On Tue, 2017-08-15 at 08:42 +0200, Rafał Miłecki wrote: >>> On 2017-08-15 08:08, Zhang Rui wrote: >>>> >>>>> >>>>> diff --git a/drivers/thermal/broadcom/Kconfig >>>>> b/drivers/thermal/broadcom/Kconfig >>>>> index 42c098e..c106a15 100644 >>>>> --- a/drivers/thermal/broadcom/Kconfig >>>>> +++ b/drivers/thermal/broadcom/Kconfig >>>>> @@ -6,6 +6,13 @@ config BCM2835_THERMAL >>>>>   help >>>>>     Support for thermal sensors on Broadcom bcm2835 SoCs. >>>>>   >>>>> +config BRCMSTB_THERMAL >>>>> + tristate "Broadcom STB AVS TMON thermal driver" >>>>> + depends on ARCH_BRCMSTB || COMPILE_TEST >>>>> + help >>>>> +   Enable this driver if you have a Broadcom STB SoC and >>>>> would like >>>>> +   thermal framework support. >>>>> + >>>> I don't understand why I got the following checkpatch warning >>>> >>>> WARNING: please write a paragraph that describes the config symbol >>>> fully >>>> #73: FILE: drivers/thermal/broadcom/Kconfig:9: >>>> +config BRCMSTB_THERMAL >>>> >>>> I didn't see this for other Kconfig changes. >>> It's because your help message is only 2 lines long (instead of 3). >>> >>> Some (many?) maintainers aren't pedantic about that, a common sense >>> should be applied ;) >> >> thanks for explaining. >> Patch 1 and 2 queued for next merge window. > > Humm, I don't see this driver in your latest 4.14 pull request to Linus, so what happened here exactly? Can we expect this driver to be submitted for 4.14 or we just happened to have missed this window now? > -- > Florian > -- Florian