Received: by 10.223.176.46 with SMTP id f43csp4522439wra; Tue, 23 Jan 2018 10:28:04 -0800 (PST) X-Google-Smtp-Source: AH8x225nzvj/Dd7OcirKTWNcyiFzeFyhOmn8LaZODCm8jWrzlz65csOZSVfdbX3PaAftjdXEazNy X-Received: by 10.107.9.200 with SMTP id 69mr4790789ioj.289.1516732084083; Tue, 23 Jan 2018 10:28:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516732084; cv=none; d=google.com; s=arc-20160816; b=Zq/7Jbv3q5bLphuP+tjdSRzui18U/lR3mBqMS269FuKIhL3YWfXwJ8MR67YNgb1gyM 9kd8yHs2Scq0R7FTLwa9K5OTnCf6gxQVp7k+jX8pbEGOcqauJCGhpPdkOWl6VH1YPcSR erSi5wSlv5UtvBA+cGQYPZkC2O9fVkzQiehVXCKFoSxSvp6+BMqIk5uYASgZblYGDryh HjYcmrn/fKIxwCZqZUbI0PAuR0vL8r09/Z+tWkNLdpwY6S0ThAqD6WUwSBGJu/3dkEOP NJMMJmLAVdndMJAnK/484+ea3dKsh2GvljEC1BMKvrUw7pa3vk4izt9UTBuZxzpHYZgf ug1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=en651+BPk90U6QgKyLRbOw2Ln0rqtnRtdgdFARMWfD0=; b=wypbk96GhAKqE/3BBfwAqB+ac3bZOtEM7t7/w3oBfJNr0EBL8ykQEO1ol+SOk6KW0P gNCGfIsUgNuuMx7kx9qv8eJue7i9YCg1Uh83iphdnbgMypdflVl52WefKe6sufbmt0nX DReGdcGd4T3AQRo3soJjtENbBDvMynT7ZPhyxhN7Dvlf6sPmo4Ik4bgArsnjSKBEx6nf csWa3Zxj8oMrDJdMpOEQKXH9TnS74ARL5KHOJlC19rOPLptt6bDtMjBab77hf14GYLop X4zk7Ov1yi1VkU5qEGqRV32z3A6EiEOjWImpUMTeWby9c/jGmc8owVwUxLnxZEmQ/h3w hRSw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x63si8701275itf.27.2018.01.23.10.27.51; Tue, 23 Jan 2018 10:28:04 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752206AbeAWS1A (ORCPT + 99 others); Tue, 23 Jan 2018 13:27:00 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:65464 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751721AbeAWS06 (ORCPT ); Tue, 23 Jan 2018 13:26:58 -0500 X-UUID: b746e6de67c8442dade2406d0ad67d31-20180124 Received: from mtkcas08.mediatek.inc [(172.21.101.126)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1081990482; Wed, 24 Jan 2018 02:26:55 +0800 Received: from mtkcas07.mediatek.inc (172.21.101.84) by mtkmbs02n2.mediatek.inc (172.21.101.101) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 24 Jan 2018 02:26:54 +0800 Received: from [172.21.77.33] (172.21.77.33) by mtkcas07.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1210.3 via Frontend Transport; Wed, 24 Jan 2018 02:26:54 +0800 Message-ID: <1516732014.15199.38.camel@mtkswgap22> Subject: Re: [PATCH] cpufreq: mediatek: Add mediatek related projects into blacklist From: Sean Wang To: Greg KH CC: , , , , , , , , Andrew-sh Cheng , Kevin Hilman Date: Wed, 24 Jan 2018 02:26:54 +0800 In-Reply-To: <20180123094205.GA14587@kroah.com> References: <8193c5fd73ee34b59799fdf5c6cc24ca60971d6e.1516693333.git.sean.wang@mediatek.com> <20180123084651.GA26581@kroah.com> <1516700314.12197.48.camel@mtkswgap22> <20180123094205.GA14587@kroah.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2018-01-23 at 10:42 +0100, Greg KH wrote: > On Tue, Jan 23, 2018 at 05:38:34PM +0800, Sean Wang wrote: > > On Tue, 2018-01-23 at 09:46 +0100, Greg KH wrote: > > > On Tue, Jan 23, 2018 at 04:31:11PM +0800, sean.wang@mediatek.com wrote: > > > > From: Sean Wang > > > > > > > > commit 6066998cbd2b1012a8d5bc9a2957cfd0ad53150e upstream. > > > > > > > > commit edeec420de24 ("cpufreq: dt-platdev: Automatically create cpufreq > > > > device with OPP v2") not added MediaTek SoCs to the blacklist that would > > > > lead to cause an occasional hang or unexpected behaviors on related boards > > > > as kernelci reported and complained on [1] specifically for 4.14 and 4.15 > > > > tree. > > > > > > > > For those reasons, add MediaTek SoCs into cpufreq-dt blacklist and wish > > > > the patch be applied to 4.14 and 4.15 tree to allow kernelci able to > > > > complete following automated kernel testing. > > > > > > > > [1] https://kernelci.org/boot/mt7623n-bananapi-bpi-r2/ > > > > > > > > Fixes: edeec420de24 (cpufreq: dt-cpufreq: platdev Automatically create device with OPP v2) > > > > Signed-off-by: Andrew-sh Cheng > > > > Signed-off-by: Sean Wang > > > > Cc: Kevin Hilman > > > > --- > > > > drivers/cpufreq/cpufreq-dt-platdev.c | 8 ++++++++ > > > > 1 file changed, 8 insertions(+) > > > > > > What stable kernel tree(s) are you wanting this backported to? > > > > > > thanks, > > > > > > greg k-h > > > > Hi, Greg, > > > > thanks for your help! > > > > stable and stable-rc are those trees I want this backported to > > I don't understand, what exactly do you mean by this? > > Have you read: > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > for how to do this properly? > > > Hi, Viresh > > > > currently, can the patch be permitted to go through tree linux-pm branch > > master to be part of mainline? > > Wait, this is not in Linus's tree already? If not, what is that big > "commit XXXX upstream" in the changelog for? > > I don't see that commit in Linus's tree at all. > > totally confused, > > greg k-h Hi Greg, thanks for your instructions Sorry for that I missed one thing: The patch is currently not in Linus tree, but it is already in linux-next tree. So, I will wait until the patch ends up in Linus's tree and submit again to wish the patch be applied into 4.14.y tree or 4.15.y tree in the near future. Sean