From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x225fsQRKf3en4zRYaUsD/ITSHAiBdmg23/7XWTFxph2ALToq98UgnysGrN6kJz+OtCxFLNJ2 ARC-Seal: i=1; a=rsa-sha256; t=1516732018; cv=none; d=google.com; s=arc-20160816; b=i28LvmXk3recBB3S0kqH10xC5h6zJdk+5ewilE0+QWjtQBKfQWRsrzbVZZzIVaphNx l8qfohjIVil9IUPp5c9CGfExVB6s8nz/j74KHxXXEZd7LlMwtlhn4rgRpSD/g8jgjcAC 5tciSvvs9HvcuMNQNmdLgLMr9fREmukg5YxrTMcTIrp+u8or+FqRuZYNgtqdCqDEW6gJ HLq9Ic8kglSf2DOIqBBGDYj36Jvy/nUXjNjwqZthxMojyLvGAn7lRWRVYKp3bKoScWeg 2/E5DCl7nV7kasWcOv7p5Ny3L5aqslOKzNI4ipRPDTtHfyzWSeiEWyF8KFYHPCm31TJt fbNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:content-transfer-encoding:references:in-reply-to:date :cc:to:from:subject:message-id:arc-authentication-results; bh=en651+BPk90U6QgKyLRbOw2Ln0rqtnRtdgdFARMWfD0=; b=dBQ1yn5tsvOyNDRQ9Gi1fz6tYu3iwnGg+Z5Vhk0wkzn41i+912XF/nbIcr3qzxj+AV MiD4J6txiqVJg12FUNyf5JMSZqmayYg4mRQ3oqMgmWlKLZpQUZxlJxBUq2DRWPgq4EKu Wb6mB4WTjr53bYKxVYwZoJ1n8hG4FZXSb1R6cnLL0+fqtp+4QeE5OBrGADIXK+Zy+lsJ rE3tgqNYos6I+GCJJ5WOzh6A/LyYODvNNFUUJe3Z1PWO8m/p3TvWZRIbLXDSqMtvzouW kd8ZWJQ1yyM15tuK5+tGgO0S3pDZ43cquxvnSIh8JmlJwuUFmXpJULGoZy9VIqjhWXKz iwjQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of sean.wang@mediatek.com designates 210.61.82.184 as permitted sender) smtp.mailfrom=sean.wang@mediatek.com Authentication-Results: mx.google.com; spf=pass (google.com: domain of sean.wang@mediatek.com designates 210.61.82.184 as permitted sender) smtp.mailfrom=sean.wang@mediatek.com X-UUID: b746e6de67c8442dade2406d0ad67d31-20180124 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 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-LABELS: =?utf-8?b?IlxcSW1wb3J0YW50Ig==?= X-GMAIL-THRID: =?utf-8?q?1590375553596139952?= X-GMAIL-MSGID: =?utf-8?q?1590408793086529325?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: 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