All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: sean.wang@mediatek.com
Cc: stable@vger.kernel.org, rjw@rjwysocki.net,
	viresh.kumar@linaro.org, matthias.bgg@gmail.com,
	linux-mediatek@lists.infradead.org, linux-pm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Andrew-sh Cheng <andrew-sh.cheng@mediatek.com>,
	Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH] cpufreq: mediatek: Add mediatek related projects into blacklist
Date: Tue, 23 Jan 2018 09:46:51 +0100	[thread overview]
Message-ID: <20180123084651.GA26581@kroah.com> (raw)
In-Reply-To: <8193c5fd73ee34b59799fdf5c6cc24ca60971d6e.1516693333.git.sean.wang@mediatek.com>

On Tue, Jan 23, 2018 at 04:31:11PM +0800, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.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@mediatek.com>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> Cc: Kevin Hilman <khilman@baylibre.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

WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: mediatek: Add mediatek related projects into blacklist
Date: Tue, 23 Jan 2018 09:46:51 +0100	[thread overview]
Message-ID: <20180123084651.GA26581@kroah.com> (raw)
In-Reply-To: <8193c5fd73ee34b59799fdf5c6cc24ca60971d6e.1516693333.git.sean.wang@mediatek.com>

On Tue, Jan 23, 2018 at 04:31:11PM +0800, sean.wang at mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.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@mediatek.com>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> Cc: Kevin Hilman <khilman@baylibre.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

  reply	other threads:[~2018-01-23  8:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  8:31 [PATCH] cpufreq: mediatek: Add mediatek related projects into blacklist sean.wang
2018-02-13  9:54 ` sean.wang
2018-02-13  9:54 ` sean.wang at mediatek.com
2018-01-23  8:46 ` Greg KH [this message]
2018-01-23  8:46   ` Greg KH
2018-01-23  9:38   ` Sean Wang
2018-01-23  9:38     ` Sean Wang
2018-01-23  9:38     ` Sean Wang
2018-01-23  9:42     ` Greg KH
2018-01-23  9:42       ` Greg KH
2018-01-23 18:26       ` Sean Wang
2018-01-23 18:26         ` Sean Wang
2018-01-23 18:26         ` Sean Wang
2018-01-24  3:03     ` Viresh Kumar
2018-01-24  3:03       ` Viresh Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180123084651.GA26581@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew-sh.cheng@mediatek.com \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=rjw@rjwysocki.net \
    --cc=sean.wang@mediatek.com \
    --cc=stable@vger.kernel.org \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.