From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Vabhav Sharma <vabhav.sharma@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Andy Tang <andy.tang@nxp.com>,
Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>
Subject: Re: [PATCH v4] cpufreq: qoriq: add support for lx2160a
Date: Wed, 01 May 2019 12:42:47 +0200 [thread overview]
Message-ID: <13001529.XdfgQYjzVm@kreacher> (raw)
In-Reply-To: <20190429051637.d5y4cfiekrysli3w@vireshk-i7>
On Monday, April 29, 2019 7:16:37 AM CEST Viresh Kumar wrote:
> On 26-04-19, 06:55, Vabhav Sharma wrote:
> > Enable support of NXP SoC lx2160a to handle the
> > lx2160a SoC.
> >
> > Signed-off-by: Tang Yuantian <andy.tang@nxp.com>
> > Signed-off-by: Yogesh Gaur <yogeshnarayan.gaur@nxp.com>
> > Signed-off-by: Vabhav Sharma <vabhav.sharma@nxp.com>
> > Acked-by: Scott Wood <oss@buserror.net>
> > Acked-by: Stephen Boyd <sboyd@kernel.org>
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > Changes for v4:
> > - Incorporated review comments from Stephen Boyd
> >
> > Changes for v3:
> > - Incorporated review comments of Rafael J. Wysocki
> > - Updated commit message
> >
> > Changes for v2:
> > - Subject line updated
> >
> > drivers/cpufreq/qoriq-cpufreq.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/cpufreq/qoriq-cpufreq.c b/drivers/cpufreq/qoriq-cpufreq.c
> > index 4295e54..81f0288 100644
> > --- a/drivers/cpufreq/qoriq-cpufreq.c
> > +++ b/drivers/cpufreq/qoriq-cpufreq.c
> > @@ -284,6 +284,7 @@ static const struct of_device_id node_matches[] __initconst = {
> > { .compatible = "fsl,ls1046a-clockgen", },
> > { .compatible = "fsl,ls1088a-clockgen", },
> > { .compatible = "fsl,ls2080a-clockgen", },
> > + { .compatible = "fsl,lx2160a-clockgen", },
> > { .compatible = "fsl,p4080-clockgen", },
> > { .compatible = "fsl,qoriq-clockgen-1.0", },
> > { .compatible = "fsl,qoriq-clockgen-2.0", },
>
> @Rafael, please apply this version. Thanks.
Done, thanks!
prev parent reply other threads:[~2019-05-01 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 6:55 Vabhav Sharma
2019-04-29 5:16 ` Viresh Kumar
2019-05-01 10:42 ` 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=13001529.XdfgQYjzVm@kreacher \
--to=rjw@rjwysocki.net \
--cc=andy.tang@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=vabhav.sharma@nxp.com \
--cc=viresh.kumar@linaro.org \
--cc=yogeshnarayan.gaur@nxp.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
all inboxes | Powered by JetHome®