From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Use IS_ENABLED() instead of checking for built-in or module
Date: Wed, 04 May 2016 23:21:12 +0200 [thread overview]
Message-ID: <1640438.89cURul1Mm@vostro.rjw.lan> (raw)
In-Reply-To: <20160427020140.GU17047@vireshk-i7>
On Wednesday, April 27, 2016 07:31:40 AM Viresh Kumar wrote:
> On 26-04-16, 20:14, Javier Martinez Canillas wrote:
> > The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either
> > built-in or as a module, use that macro instead of open coding the same.
> >
> > Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
> >
> > ---
> >
> > drivers/cpufreq/e_powersaver.c | 14 +++++++-------
> > drivers/cpufreq/ppc_cbe_cpufreq.h | 2 +-
> > 2 files changed, 8 insertions(+), 8 deletions(-)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied, thanks!
prev parent reply other threads:[~2016-05-04 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 0:14 [PATCH] cpufreq: Use IS_ENABLED() instead of checking for built-in or module Javier Martinez Canillas
2016-04-27 2:01 ` Viresh Kumar
2016-05-04 21:21 ` 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=1640438.89cURul1Mm@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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