Linux Power Management development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Mark Brown <broonie@kernel.org>,
	Nishanth Menon <menon.nishanth@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	Mark Brown <broonie@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] PM / OPP: Make OPP invisible to users in Kconfig
Date: Tue, 20 May 2014 01:19:45 +0200	[thread overview]
Message-ID: <2738394.FHGFLADJqP@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpo=xtnHyWcjHxmSPgzdovMshgotMkQj6Y__R9UvzzfTyHw@mail.gmail.com>

On Monday, May 12, 2014 09:40:46 AM Viresh Kumar wrote:
> On 9 May 2014 23:48, Mark Brown <broonie@kernel.org> wrote:
> > From: Mark Brown <broonie@linaro.org>
> >
> > The OPP code is an in kernel library selected by its users, there is no
> > no architecture code required to implement it and enabling it without a
> 
> s/no no/no
> 
> > user just increases the kernel size. Since the users select rather than
> > depend on it just remove the ability to directly set the option from
> > Kconfig.
> >
> > Signed-off-by: Mark Brown <broonie@linaro.org>
> > ---
> >
> > This leaves the ARCH_HAS_OPP symbol since removing that requires
> > updating the relevant architectures, if this is OK I can sumbit a
> > followup patch cleaning that up.
> >
> >  kernel/power/Kconfig | 3 +--
> >  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

Queued up for 3.16, thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2014-05-19 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 18:18 [PATCH] PM / OPP: Make OPP invisible to users in Kconfig Mark Brown
2014-05-09 18:56 ` Nishanth Menon
2014-05-12  4:10 ` Viresh Kumar
2014-05-19 23:19   ` Rafael J. Wysocki [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=2738394.FHGFLADJqP@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=broonie@kernel.org \
    --cc=broonie@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=menon.nishanth@gmail.com \
    --cc=viresh.kumar@linaro.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