linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Rafael Wysocki <rjw@rjwysocki.net>
Cc: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	eric.engestrom@imgtec.com, rufus.hamade@imgtec.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / OPP: Move CONFIG_OF dependent code in a separate file
Date: Thu, 5 May 2016 15:00:11 +0100	[thread overview]
Message-ID: <572B51EB.1080505@arm.com> (raw)
In-Reply-To: <1f90c873e5801967acbb2e38fe0b268189247049.1462445391.git.viresh.kumar@linaro.org>



On 05/05/16 11:50, Viresh Kumar wrote:
> Recently few issues were noticed in the code where CONFIG_OF wasn't
> consistently used for many routines. The core file is big enough now and
> ifdef hackery makes it less readable.
>
> Move OF specific code to another file and compile that only if CONFIG_OF
> is enabled.
>
> Compile-tested:
> - For ARM (exynos) with CONFIG_OF enabled
> - For X86 with CONFIG_OF disabled (have to enable CONFIG_PM_OPP separately)
>

Just gave it a spin on ARM64 Juno on top of linux-pm/bleeding-edge so
you can have:

Tested-by: Sudeep Holla <sudeep.holla@arm.com>

-- 
Regards,
Sudeep

      parent reply	other threads:[~2016-05-05 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-05 10:50 [PATCH] PM / OPP: Move CONFIG_OF dependent code in a separate file Viresh Kumar
2016-05-05 13:59 ` Rafael J. Wysocki
2016-05-05 14:00 ` Sudeep Holla [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=572B51EB.1080505@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=eric.engestrom@imgtec.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=rufus.hamade@imgtec.com \
    --cc=sboyd@codeaurora.org \
    --cc=viresh.kumar@linaro.org \
    --cc=vireshk@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).