Received: by 10.192.165.156 with SMTP id m28csp1278106imm; Wed, 18 Apr 2018 07:12:10 -0700 (PDT) X-Google-Smtp-Source: AIpwx49FBq3U8f8mYJ1fuN0h2WkSS3vSvK4gqA3QbK64flVRILUfkb8g0b5+fCHsYlIthiPJMOE5 X-Received: by 2002:a17:902:102:: with SMTP id 2-v6mr2298529plb.48.1524060729726; Wed, 18 Apr 2018 07:12:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524060729; cv=none; d=google.com; s=arc-20160816; b=XiPCYpPRxM5m2o0iVFa6+XQmeFqLcl0EJpbRZzX0fs9jslr2t0DNXQ01UXfd1ZmgFn Kw2MXj1rlffDG4j2cybuQLfsza7FBSjWOcTzDejzxXVQVUUI4HC/SL5IFz5eKZ9jzExZ cEUKClyzNasiP5MqjjoD4poCsiRb+6ZbJu0ozFbJWNkqcaLhAB944L0vt9mdnr5LdyUQ jNFEk7oJA+pM9rwKiy3FjeMGjxFCXZerbQXP7H5sIi5JQ/eeGuzBZsg9U9e6bXvQgBpI GBQ3Oz2Z1DtGT9jNsQWSl4/kEXJThwF4UC0KcJUzeuv8PDCCGwrIRl0SNzYke7fU5hdY kMRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=Rry15u1zGMKywiOilzxB5aKs+XODtV8c8ru+ssnjm8M=; b=iBYuX2AY2wLshVufyKReUcrTfE4ySmVTrz+FW+dqEK2rQYHqzcYEzwwX4C9jZbkpno LPjf856NKO3mQVGuxAGJr5DE8UICKy6S6qxVBVaOhZA66itGaPR96r0xzdr2qYQchVEt RtgEyJnb+rCVDPII2B2xFt+CkoOQ/UwDQH3Pkg1oWEjbQ627RhKBcyZSXGVg6y89MdQa HyCkcPxgOJfjjFYaUBauexRQg3eup2m9l9qpWC48shdEFEpzTKxy5mtWaUsYUfXXlT1I xPOxFrqR/S8O5B7H6YBnHab9adtJb7qctDiCRhG+rMRosxiQr1oQLkwHRAgydjXX9aIe YgYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tB44UrZM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v7si1235791pfi.28.2018.04.18.07.11.55; Wed, 18 Apr 2018 07:12:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tB44UrZM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753596AbeDROKo (ORCPT + 99 others); Wed, 18 Apr 2018 10:10:44 -0400 Received: from mail-wr0-f175.google.com ([209.85.128.175]:36639 "EHLO mail-wr0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752659AbeDROKl (ORCPT ); Wed, 18 Apr 2018 10:10:41 -0400 Received: by mail-wr0-f175.google.com with SMTP id q13-v6so5273261wre.3; Wed, 18 Apr 2018 07:10:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=Rry15u1zGMKywiOilzxB5aKs+XODtV8c8ru+ssnjm8M=; b=tB44UrZM9ddv0gyuCFsQ1VpK/VXMfnwGn3iM/bHoKxxyozClKo3At3D6S9pyqr/Ch+ JIf7qsUS39enV+SugpJ5LRerA9KwWOoU3vUhvZGuVKPfCELPWdhCoPt3mM9BzldrAoUH qxa162cKYS0ke0fhVrCVWS5GDIzAsfAlAt2mafTWfvzErYdoPGPdiXZQfgnU2ITUKuBk oEbni8xaorFXA5HlA1MonCdWlbdLzL2kEtkOrna92I8MKW/gHLLRj2V/T9e9Q1iuFw0V dns9m3FAZ/TNcdwGEFTjIicLDbrWAczrSqam3twZWyjxGfjuwFKKlAOGo+w8S2X+1Xnl z4Mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=Rry15u1zGMKywiOilzxB5aKs+XODtV8c8ru+ssnjm8M=; b=ND19kyjA3pWvdpnnTBKAufY9fhPbnrgiWwNn/RZ0HlZs6L1KYodLqqOza/wkEg1wxZ 9aXCg/UWSG8eR8JtrfMVrSC6f0LErHxeiPV/lg1oAxmwPhvY+jyd8bS/2IfeNwGVIw25 sNYYe150mOJP0bs21ozSQKMsQauWuxPEEKZmjJhLjsuzskJnuB2vZYmHF+zX/7qOo5tg s3raTF2yIs+3NEFfDGFGdN7NsxjTKLaSHfzT1tWqppB2SmLtAW4E5P6LM+zH8Jah9SJJ MD5YaatAJGJY6GicR24EHQyZ2c1OZzG8r5hpJbJ14mruL9KNHL3tN9/lFMY6wV2N/Teb 1P2g== X-Gm-Message-State: ALQs6tC2cw3/6WGgnSBn2z2ngWQt0YPkX05CXFmXSOuDpJT+UAOMv08J EQEyWgsVNjXde5+oYgbfsFs= X-Received: by 2002:adf:9f01:: with SMTP id l1-v6mr1828882wrf.207.1524060639491; Wed, 18 Apr 2018 07:10:39 -0700 (PDT) Received: from localhost.localdomain (host113-247-static.87-94-b.business.telecomitalia.it. [94.87.247.113]) by smtp.gmail.com with ESMTPSA id v66sm2045455wmd.4.2018.04.18.07.10.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Apr 2018 07:10:38 -0700 (PDT) Date: Wed, 18 Apr 2018 07:10:30 -0700 From: Eduardo Valentin To: Zhang Rui Cc: ACPI Devel Maling List , Linux PM , LKML Subject: Re: [GIT PULL V3] Thermal SoC management updates for v4.17-rc1 Message-ID: <20180418141027.GA3303@localhost.localdomain> References: <20180414183051.GA27921@localhost.localdomain> <1524037889.2553.13.camel@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1524037889.2553.13.camel@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Wed, Apr 18, 2018 at 03:51:29PM +0800, Zhang Rui wrote: > Hi, Eduardo, > > On 六, 2018-04-14 at 11:30 -0700, Eduardo Valentin wrote: > > Hello Linus, > > > > Please find thermal-soc changes for v4.17-rc1. > > Rui asked me to send the pull request directly to you > > as we are close to the end of the merge window. > > Essentially this pull removes the series that caused > > warning regression. I will work with the developer > > to get that fixed later on, but I am still sending > > the other few patches that are unrelated to that. > > Let me know if this causes any issues and can still > > be pulled. > > > > Changelog: > > - New i.MX7 thermal sensor > > - Mediatek driver now supports MT7622 SoC > > - Removal of min max cpu cooling DT property > > > > Differences in V3: > > - Rebased on top current linus/master, to avoid and merge issues > > from previous pulled thermal code. > > > > Differences in V2: > > - Reordered the patches to drop exynos changes for now until we get > > agreement on the fix on that driver for the compilation warns > > caused by the confusing conversion functions. > > > > > > The following changes since commit > > 48023102b7078a6674516b1fe0d639669336049d: > > > >   Merge branch 'overlayfs-linus' of > > git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs (2018-04- > > 13 16:55:41 -0700) > > > > are available in the git repository at: > > > >   git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc- > > thermal linus > > > > for you to fetch changes up to > > 15a32df1918259be6c23fc36014fc26ee66c836c: > > > >   dt-bindings: thermal: Remove "cooling-{min|max}-level" properties > > (2018-04-14 09:37:55 -0700) > > > This pull request does not catch this merge window. > So do you want to split it into 2 separate pull requests, one for 4.17- > rc and another for 4.18-rc1? OK. Yeah, I am fine with that. > > > ---------------------------------------------------------------- > > Anson Huang (1): > >       thermal: imx: add i.MX7 thermal sensor support > > > > Bartlomiej Zolnierkiewicz (1): > >       dt-bindings: thermal: remove no longer needed samsung thermal > > properties > > > > Sean Wang (2): > >       dt-bindings: thermal: add binding for MT7622 SoC > >       thermal: mediatek: add support for MT7622 SoC > > > > Viresh Kumar (1): > >       dt-bindings: thermal: Remove "cooling-{min|max}-level" > > properties > > > IMO, together with the refreshed exynos fixes, the one from Viresh and > the one from Bartlomiej can be queued for 4.17-rc, and the others have > to wait until next merge window. > Correct, the new chip support will need to wait for the next merge window. I have already split the patches into the two categories. The patches removing stuff are in my -fixes branch. All the other adding new chip support are in my -linus branch. Now, Do you have anything for this -rc2 ? If not, I will send directly to Linus the stuff in my -fixes branch. Let me know. Eduardo