All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	YueHaibing <yuehaibing@huawei.com>
Cc: ilia.lin@gmail.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: qcom-kryo: add NULL entry to the end of_device_id array
Date: Thu, 26 Jul 2018 11:05:05 +0200	[thread overview]
Message-ID: <4102618.ESNx517Qjd@aspire.rjw.lan> (raw)
In-Reply-To: <20180724034335.v76tfqk2imlyf2eg@vireshk-i7>

On Tuesday, July 24, 2018 5:43:35 AM CEST Viresh Kumar wrote:
> On 23-07-18, 20:34, YueHaibing wrote:
> > Make sure of_device_id tables are NULL terminated
> > Found by coccinelle spatch "misc/of_table.cocci"
> > 
> > Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> > ---
> >  drivers/cpufreq/qcom-cpufreq-kryo.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/cpufreq/qcom-cpufreq-kryo.c b/drivers/cpufreq/qcom-cpufreq-kryo.c
> > index 29389ac..efc9a7a 100644
> > --- a/drivers/cpufreq/qcom-cpufreq-kryo.c
> > +++ b/drivers/cpufreq/qcom-cpufreq-kryo.c
> > @@ -183,6 +183,7 @@ static struct platform_driver qcom_cpufreq_kryo_driver = {
> >  static const struct of_device_id qcom_cpufreq_kryo_match_list[] __initconst = {
> >  	{ .compatible = "qcom,apq8096", },
> >  	{ .compatible = "qcom,msm8996", },
> > +	{}
> >  };
> >  
> >  /*
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> 
> 

Patch applied, thanks!



      reply	other threads:[~2018-07-26  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 12:34 [PATCH] cpufreq: qcom-kryo: add NULL entry to the end of_device_id array YueHaibing
2018-07-23 12:34 ` YueHaibing
2018-07-23 12:44 ` Ilia Lin
2018-07-24  3:43 ` Viresh Kumar
2018-07-26  9:05   ` 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=4102618.ESNx517Qjd@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=ilia.lin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.