[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180123094205.GA14587@kroah.com>
Date: Tue, 23 Jan 2018 10:42:05 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Sean Wang <sean.wang@...iatek.com>
Cc: stable@...r.kernel.org, rjw@...ysocki.net, viresh.kumar@...aro.org,
matthias.bgg@...il.com, linux-mediatek@...ts.infradead.org,
linux-pm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Andrew-sh Cheng <andrew-sh.cheng@...iatek.com>,
Kevin Hilman <khilman@...libre.com>
Subject: Re: [PATCH] cpufreq: mediatek: Add mediatek related projects into
blacklist
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@...iatek.com wrote:
> > > From: Sean Wang <sean.wang@...iatek.com>
> > >
> > > 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 <andrew-sh.cheng@...iatek.com>
> > > Signed-off-by: Sean Wang <sean.wang@...iatek.com>
> > > Cc: Kevin Hilman <khilman@...libre.com>
> > > ---
> > > 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
Powered by blists - more mailing lists