From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 2/4] cpufreq: mediatek: Add mediatek related projects into blacklist
Date: Mon, 22 Jan 2018 15:46:45 +0530 [thread overview]
Message-ID: <20180122101645.GG2421@vireshk-i7> (raw)
In-Reply-To: <1516610369.12197.20.camel@mtkswgap22>
On 22-01-18, 16:39, Sean Wang wrote:
> Hi, Rafael and Viresh
>
> Can you kindly guide me how to let the patch also be applied to 4.14 and
> 4.15 tree? Do I need to submit another patches for them?
>
> These trees really need them. Otherwise, multi_v7_defconfig setup will
> cause an occasional hang or unexpected behaviors on related boards as
> [1] kernelci reported :-(
You need to send them for stable kernels, just follow the following doc on how
to send patches for stable kernels.
Documentation/process/stable-kernel-rules.rst
--
viresh
next prev parent reply other threads:[~2018-01-22 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 6:07 [PATCH v1 0/4] add support of cpufreq to mt8173 and mt2712 Andrew-sh Cheng
2017-12-08 6:07 ` [PATCH v1 1/4] cpufreq: mediatek: add mt2712 into compatible list Andrew-sh Cheng
2017-12-11 7:54 ` Viresh Kumar
2017-12-08 6:07 ` [PATCH v1 2/4] cpufreq: mediatek: Add mediatek related projects into blacklist Andrew-sh Cheng
2017-12-11 7:55 ` Viresh Kumar
2018-01-22 8:39 ` Sean Wang
2018-01-22 10:16 ` Viresh Kumar [this message]
2017-12-08 6:07 ` [PATCH v1 3/4] arm64: dts: mediatek: add mt8173 cpufreq related device nodes Andrew-sh Cheng
2017-12-11 7:56 ` Viresh Kumar
2017-12-08 6:07 ` [PATCH v1 4/4] arm64: dts: mediatek: add mt2712 " Andrew-sh Cheng
2017-12-11 7:57 ` Viresh Kumar
2017-12-12 1:17 ` Rafael J. Wysocki
2017-12-12 7:26 ` Viresh Kumar
2017-12-12 9:34 ` Matthias Brugger
2017-12-17 18:05 ` Rafael J. Wysocki
2017-12-20 14:47 ` Matthias Brugger
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=20180122101645.GG2421@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox