From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] PM / devfreq: Fix module autoload for platform drivers
Date: Thu, 20 Oct 2016 11:24:10 +0900 [thread overview]
Message-ID: <58082ACA.90104@samsung.com> (raw)
In-Reply-To: <1476911187-11040-1-git-send-email-javier@osg.samsung.com>
Hi Javier,
On 2016? 10? 20? 06:06, Javier Martinez Canillas wrote:
> Hello,
>
> I noticed that module autoload won't be working in some of the defreq
> platform drivers. This patch series contains the fixes for these.
>
> Best regards,
> Javier
>
>
> Javier Martinez Canillas (4):
> PM / devfreq: rk3399_dmc: Fix module autoload
> PM / devfreq: exynos-nocp: Fix module autoload
> PM / devfreq: rockchip-dfi: Fix module autoload
> PM / devfreq: exynos-ppmu: Fix module autoload
>
> drivers/devfreq/event/exynos-nocp.c | 1 +
> drivers/devfreq/event/exynos-ppmu.c | 1 +
> drivers/devfreq/event/rockchip-dfi.c | 1 +
> drivers/devfreq/rk3399_dmc.c | 1 +
> 4 files changed, 4 insertions(+)
>
Looks good to me of all patches.
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
--
Best Regards,
Chanwoo Choi
next prev parent reply other threads:[~2016-10-20 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161019210649epcas1p4e0c178cb75709bb242da10d9c1fd77d2@epcas1p4.samsung.com>
2016-10-19 21:06 ` [PATCH 0/4] PM / devfreq: Fix module autoload for platform drivers Javier Martinez Canillas
2016-10-19 21:06 ` [PATCH 2/4] PM / devfreq: exynos-nocp: Fix module autoload Javier Martinez Canillas
2016-10-19 21:06 ` [PATCH 3/4] PM / devfreq: rockchip-dfi: " Javier Martinez Canillas
2016-10-19 21:06 ` [PATCH 4/4] PM / devfreq: exynos-ppmu: " Javier Martinez Canillas
2016-10-20 2:24 ` Chanwoo Choi [this message]
[not found] <CGME20161019210645epcas1p449463edf9c3cb3681b0a4e8116ccf7f2@epcas1p4.samsung.com>
2016-10-20 2:22 ` [PATCH 0/4] PM / devfreq: Fix module autoload for platform drivers MyungJoo Ham
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=58082ACA.90104@samsung.com \
--to=cw00.choi@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).