public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@arm.com>
To: linux-pm@vger.kernel.org
Cc: linux-samsung-soc@vger.kernel.org, orjan.eide@arm.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] Convert exynos PPMU driver to be built as module
Date: Wed, 06 Aug 2014 14:41:26 +0100	[thread overview]
Message-ID: <9hhvbq54tx5.fsf@arm.com> (raw)
In-Reply-To: <1405692594-19352-1-git-send-email-punit.agrawal@arm.com> (Punit Agrawal's message of "Fri, 18 Jul 2014 15:09:52 +0100")

Punit Agrawal <punit.agrawal@arm.com> writes:

> Hi,
>
> There's no reason why the exynos PPMU can't be built as a module
> except you need -
>
> - The first patch exports the functions that are needed to build
> devfreq drivers as modules.
>
> - The second patch then converts the exynos PPMU devfreq driver to be
>   built as a module.
>

Ping!

> Compile tested only.
>
> Thanks
>
> Punit Agrawal (1):
>   PM / devfreq: exynos: Enable building exynos PPMU as module
>
> Ørjan Eide (1):
>   PM / devfreq: Export helper functions for drivers
>
>  drivers/devfreq/Kconfig              |    2 +-
>  drivers/devfreq/devfreq.c            |    3 +++
>  drivers/devfreq/exynos/exynos_ppmu.c |    3 +++
>  3 files changed, 7 insertions(+), 1 deletion(-)

      parent reply	other threads:[~2014-08-06 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 14:09 [PATCH 0/2] Convert exynos PPMU driver to be built as module Punit Agrawal
2014-07-18 14:09 ` [PATCH 1/2] PM / devfreq: Export helper functions for drivers Punit Agrawal
2014-08-12 13:49   ` Hernandez, Carlos
2014-07-18 14:09 ` [PATCH 2/2] PM / devfreq: exynos: Enable building exynos PPMU as module Punit Agrawal
2014-08-06 13:41 ` Punit Agrawal [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=9hhvbq54tx5.fsf@arm.com \
    --to=punit.agrawal@arm.com \
    --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=orjan.eide@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