From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Lukasz Luba <lukasz.luba@arm.com>
Subject: Re: [PATCH 2/4] cpuidle: big.LITTLE: enable driver only on Peach-Pit/Pi Chromebooks
Date: Mon, 24 Aug 2020 10:15:42 +0200 [thread overview]
Message-ID: <f46e7041-f75e-8d97-e967-2ac458aaaf2e@linaro.org> (raw)
In-Reply-To: <20200817153908.GA13144@kozik-lap>
On 17/08/2020 17:39, Krzysztof Kozlowski wrote:
> On Wed, Jun 24, 2020 at 12:05:46PM +0200, Bartlomiej Zolnierkiewicz wrote:
>>
>> On 6/16/20 10:12 AM, Marek Szyprowski wrote:
>>> This driver always worked properly only on the Exynos 5420/5800 based
>>> Chromebooks (Peach-Pit/Pi), so change the required compatible string to
>>> the 'google,peach', to avoid enabling it on the other Exynos 542x/5800
>>> boards, which hangs in such case. The main difference between Peach-Pit/Pi
>>> and other Exynos 542x/5800 boards is the firmware - Peach platform doesn't
>>> use secure firmware at all.
>>>
>>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>>
>> Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>
> This patch waited on list for almost two months and was not picked up.
> Therefore I'll take it for v5.10.
It happens some patches can fall into the cracks, especially when we are
fully busy with a peak of work. Also, we have filters in our mailers
which are not perfect. A gentle ping is enough to ask to pay attention
to the series.
I can understand that is annoying, but preemptively pick the patch is
not adequate.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2020-08-24 8:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200616081248eucas1p168faa343ce333a28c8fd3cf9a6a58b3c@eucas1p1.samsung.com>
2020-06-16 8:12 ` [PATCH 0/4] Restore big.LITTLE cpuidle driver for Exynos Marek Szyprowski
[not found] ` <CGME20200616081249eucas1p151a8892ca0abfa3108955e1fc5054fc3@eucas1p1.samsung.com>
2020-06-16 8:12 ` [PATCH 1/4] ARM: exynos: Apply little core workaround only under secure firmware Marek Szyprowski
2020-06-17 16:26 ` Lukasz Luba
2020-06-22 17:19 ` Krzysztof Kozlowski
2020-06-29 8:54 ` Marek Szyprowski
2020-06-29 9:13 ` Krzysztof Kozlowski
[not found] ` <CGME20200629100230eucas1p1bf07ca4c84ba6be1fbdd80c45d077518@eucas1p1.samsung.com>
2020-06-29 10:02 ` [PATCH v2 1/4] ARM: exynos: MCPM: Restore big.LITTLE cpuidle support Marek Szyprowski
2020-06-29 11:05 ` Lukasz Luba
2020-06-29 18:28 ` Krzysztof Kozlowski
[not found] ` <CGME20200616081249eucas1p2ad165b545f265bec88a06270d55fce76@eucas1p2.samsung.com>
2020-06-16 8:12 ` [PATCH 2/4] cpuidle: big.LITTLE: enable driver only on Peach-Pit/Pi Chromebooks Marek Szyprowski
2020-06-22 17:19 ` Krzysztof Kozlowski
2020-06-24 10:05 ` Bartlomiej Zolnierkiewicz
2020-08-17 15:39 ` Krzysztof Kozlowski
2020-08-24 8:15 ` Daniel Lezcano [this message]
2020-08-24 8:26 ` Krzysztof Kozlowski
2020-08-24 9:14 ` Daniel Lezcano
[not found] ` <CGME20200616081250eucas1p2de7110898dad050866d78cb5d5120422@eucas1p2.samsung.com>
2020-06-16 8:12 ` [PATCH 3/4] ARM: exynos_defconfig: Enable big.LITTLE cpuidle driver Marek Szyprowski
2020-06-22 17:20 ` Krzysztof Kozlowski
2020-06-29 11:35 ` Marek Szyprowski
2020-06-24 10:06 ` Bartlomiej Zolnierkiewicz
[not found] ` <CGME20200616081250eucas1p2a98f8810962ddc692fa5588a74f911b3@eucas1p2.samsung.com>
2020-06-16 8:12 ` [PATCH 4/4] ARM: multi_v7_defconfig: " Marek Szyprowski
2020-06-24 10:06 ` Bartlomiej Zolnierkiewicz
2020-06-16 20:58 ` [PATCH 0/4] Restore big.LITTLE cpuidle driver for Exynos Anand Moon
2020-06-17 9:48 ` Marek Szyprowski
2020-06-17 10:40 ` Lukasz Luba
2020-06-17 10:57 ` Anand Moon
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=f46e7041-f75e-8d97-e967-2ac458aaaf2e@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukasz.luba@arm.com \
--cc=m.szyprowski@samsung.com \
/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).