Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967597AbdIZDDi (ORCPT ); Mon, 25 Sep 2017 23:03:38 -0400 Received: from mga05.intel.com ([192.55.52.43]:22569 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935664AbdIZDCM (ORCPT ); Mon, 25 Sep 2017 23:02:12 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,438,1500966000"; d="scan'208";a="132304700" From: "Zhang, Rui" To: Florian Fainelli , 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 Subject: RE: [PATCH v4 2/4] thermal: add brcmstb AVS TMON driver Thread-Topic: [PATCH v4 2/4] thermal: add brcmstb AVS TMON driver Thread-Index: AQHTEVtdcLi0oFWggkymE3kTcXWYXKKEcPMAgAAJeICAAAHRgIA/zkyAgADvaBA= Date: Tue, 26 Sep 2017 03:02:09 +0000 Message-ID: <744357E9AAD1214791ACBA4B0B9092636BE1FB55@SHSMSX101.ccr.corp.intel.com> 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> In-Reply-To: <4ec0715e-fcd7-3aec-3589-96426575c373@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v8Q341Vm001960 Content-Length: 2861 Lines: 63 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. I don’t think we can make it for 4.14. Eduardo will be back and pick the soc patches for 4.15. 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