From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: dt-platdev: drop socionext,uniphier-ld6b from whitelist
Date: Tue, 10 Oct 2017 08:55:25 +0530 [thread overview]
Message-ID: <20171010032525.GE4031@vireshk-i7> (raw)
In-Reply-To: <20170914212655.GD11836@ubuntu>
On 14-09-17, 14:26, Viresh Kumar wrote:
> On 30-08-17, 00:37, Masahiro Yamada wrote:
> > As you see arch/arm/boot/dts/uniphier-ld6b.dtsi, it includes
> > uniphier-pxs2.dtsi, which uses "operating-points-v2" property
> > and whose cpufreq device is automatically created.
> >
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > ---
> >
> > drivers/cpufreq/cpufreq-dt-platdev.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> > index a020da7940d6..c344fc1c4eb8 100644
> > --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> > @@ -83,8 +83,6 @@ static const struct of_device_id whitelist[] __initconst = {
> > { .compatible = "rockchip,rk3368", },
> > { .compatible = "rockchip,rk3399", },
> >
> > - { .compatible = "socionext,uniphier-ld6b", },
> > -
> > { .compatible = "st-ericsson,u8500", },
> > { .compatible = "st-ericsson,u8540", },
> > { .compatible = "st-ericsson,u9500", },
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
@Rafael: You missed my Ack while applying this patch ?
--
viresh
next prev parent reply other threads:[~2017-10-10 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 15:37 [PATCH] cpufreq: dt-platdev: drop socionext,uniphier-ld6b from whitelist Masahiro Yamada
2017-09-14 21:26 ` Viresh Kumar
2017-10-09 12:15 ` Masahiro Yamada
2017-10-10 3:25 ` Viresh Kumar [this message]
2017-10-10 15:45 ` Rafael J. Wysocki
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=20171010032525.GE4031@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=yamada.masahiro@socionext.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