From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] cpuidle: arm: Enable compile testing for some of drivers
Date: Mon, 13 Jan 2020 13:24:00 +0100 [thread overview]
Message-ID: <92592736-fa55-8fe8-c893-e9e7129fe910@linaro.org> (raw)
In-Reply-To: <a4fa3f89-e792-aeee-b9ea-9af244ace04a@linaro.org>
On 13/01/2020 12:58, Daniel Lezcano wrote:
> On 13/01/2020 12:51, Rafael J. Wysocki wrote:
>> On Sunday, December 29, 2019 7:09:12 PM CET Krzysztof Kozlowski wrote:
>>> Some of cpuidle drivers for ARMv7 can be compile tested on this
>>> architecture because they do not depend on mach-specific bits. Enable
>>> compile testing for big.LITTLE, Kirkwood, Zynq, AT91, Exynos and mvebu
>>> cpuidle drivers.
>>>
>>> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
>>> ---
[ ... ]
>> Daniel, any concerns regarding this one?
>
> Yes, I have a doubt about this patch. I'll double check before commenting.
Actually it is fine.
Acked-by: Daniel Lezcano <daniel.lezcano@linaro.org>
--
<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-01-13 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 18:09 [PATCH] cpuidle: arm: Enable compile testing for some of drivers Krzysztof Kozlowski
2019-12-29 18:09 ` Krzysztof Kozlowski
2020-01-13 11:51 ` Rafael J. Wysocki
2020-01-13 11:58 ` Daniel Lezcano
2020-01-13 12:24 ` Daniel Lezcano [this message]
2020-01-14 22:51 ` Rafael J. Wysocki
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=92592736-fa55-8fe8-c893-e9e7129fe910@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=b.zolnierkie@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nicolas.ferre@microchip.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.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).