From: Kever Yang <kever.yang@rock-chips•com>
To: Kevin Hilman <khilman@baylibre•com>, Heiko Stuebner <heiko@sntech•de>
Cc: kernel-build-reports@lists•linaro.org,
linux-rockchip@lists•infradead.org, linux-next@vger•kernel.org,
张晴 <elaine.zhang@rock-chips•com>, 闫孝军 <andy.yan@rock-chips•com>,
linux-arm-kernel@lists•infradead.org
Subject: Re: CPUfreq fail on rk3399-firefly
Date: Thu, 10 Oct 2019 17:32:48 +0800 [thread overview]
Message-ID: <3ed325e9-c958-c329-66b7-6eee8da06fde@rock-chips.com> (raw)
In-Reply-To: <7hh84yisd3.fsf@baylibre.com>
Hi Kevin,
I will send you a Firefly-rk3399 board to you.
Thanks,
- Kever
On 2019/9/27 上午6:51, Kevin Hilman wrote:
> This is now failing in the v5.2 stable tree.
>
> Any suggestions on what to do? otherwise, I'll just need to disable
> this board.
>
> Or, if someone wants to donate a new rk3399-firefly for my lab, I'd be
> glad to try replacing it.
>
> Kevin
prev parent reply other threads:[~2019-10-10 9:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d3057c8.1c69fb81.c6489.8ad2@mx.google.com>
2019-07-18 16:20 ` next/master boot: 285 boots: 16 failed, 264 passed with 3 offline, 1 untried/unknown, 1 conflict (next-20190718) Mark Brown
2019-08-12 17:24 ` Mark Brown
2019-08-13 17:26 ` Kevin Hilman
2019-08-13 17:35 ` CPUfreq fail on rk3399-firefly (was: next/master boot: 285 boots: 16 failed, 264 passed with 3 offline, 1 untried/unknown, 1 conflict (next-20190718)) Kevin Hilman
2019-08-14 9:01 ` Heiko Stuebner
2019-08-21 18:59 ` Kevin Hilman
2019-08-23 0:32 ` CPUfreq fail on rk3399-firefly Kever Yang
2019-08-23 16:52 ` Kevin Hilman
2019-08-23 17:03 ` Kevin Hilman
2019-08-26 9:56 ` Kever Yang
2019-08-26 17:09 ` Kevin Hilman
2019-08-27 1:54 ` Kever Yang
2019-08-27 2:14 ` Heiko Stuebner
2019-08-27 9:59 ` Kever Yang
2019-09-26 22:51 ` Kevin Hilman
2019-10-10 9:32 ` Kever Yang [this message]
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=3ed325e9-c958-c329-66b7-6eee8da06fde@rock-chips.com \
--to=kever.yang@rock-chips$(echo .)com \
--cc=andy.yan@rock-chips$(echo .)com \
--cc=elaine.zhang@rock-chips$(echo .)com \
--cc=heiko@sntech$(echo .)de \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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