From: olof@lixom.net (Olof Johansson)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] revert ARM SCPI changes for v4.15-rc1
Date: Sat, 2 Dec 2017 17:04:35 -0800 [thread overview]
Message-ID: <20171203010435.6ycn75rxss5yiixe@localhost> (raw)
In-Reply-To: <7hlgimns2m.fsf@baylibre.com>
On Fri, Dec 01, 2017 at 11:53:05AM -0800, Kevin Hilman wrote:
> Arnd, Olof,
>
> These ARM SCPI changes caused SCPI regressions resulting in CPUfreq
> failures on most Amlogic SoCs (found by kernelci.org.)
>
> Unfortunately, this was not caught in linux-next due to other
> bugs/panics on these platforms masking this problem so we've only found
> it since we've fixed the other issues.
>
> Since we're already in the -rc cycle, I'd prefer to revert to a known
> working state (that of v4.14) rather than finding/reverting a subset,
> which would just lead to another untested state.
>
> These changes can then have some time to be better reviewed and tested
> and resubmitted for v4.16.
>
> I've tested this revert on the affect Amlogic SoCs and verified that
> we're back to the previous (working) condition.
>
> Also, I'm sending the pull directly to arm-soc instead of Sudeeep
> because I understand that Sudeep is currently out-of-office and unlikely
> to be able to address this himself during the -rc cycle.
>
Sounds like the right approach here. I've merged this and added the above text
to the merge commit as well.
-Olof
next prev parent reply other threads:[~2017-12-03 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 19:53 [GIT PULL] revert ARM SCPI changes for v4.15-rc1 Kevin Hilman
2017-12-03 1:04 ` Olof Johansson [this message]
2017-12-03 16:26 ` Heiner Kallweit
2017-12-04 2:24 ` Sudeep Holla
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=20171203010435.6ycn75rxss5yiixe@localhost \
--to=olof@lixom.net \
--cc=linus-amlogic@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;
as well as URLs for NNTP newsgroup(s).