From: "MyungJoo Ham" <myungjoo.ham@samsung.com>
To: "Javier Martinez Canillas" <javier@osg.samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: FW: RE: [PATCH 0/4] PM / devfreq: Fix module autoload for platform drivers
Date: Thu, 20 Oct 2016 02:31:17 +0000 [thread overview]
Message-ID: <1458141592.1463929.1476930677746.JavaMail.weblogic@ep1ml101a> (raw)
In-Reply-To: CGME20161019210645epcas1p449463edf9c3cb3681b0a4e8116ccf7f2@epcas1p4.samsung.com
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
> > 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
>
> Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
>
> All the four are not at for-4.9-rc branch.
not --> now
> https://git.kernel.org/cgit/linux/kernel/git/mzx/devfreq.git/log/?h=for-4.9-rc
>
>
> Cheers,
> MyungJoo
>
> >
> > 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(+)
> >
> > --
> > 2.7.4
prev parent reply other threads:[~2016-10-20 2:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161019210645epcas1p449463edf9c3cb3681b0a4e8116ccf7f2@epcas1p4.samsung.com>
2016-10-20 2:22 ` [PATCH 0/4] PM / devfreq: Fix module autoload for platform drivers MyungJoo Ham
2016-10-20 2:31 ` MyungJoo Ham [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=1458141592.1463929.1476930677746.JavaMail.weblogic@ep1ml101a \
--to=myungjoo.ham@samsung.com \
--cc=javier@osg.samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.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).