All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Aisheng Dong <aisheng.dong@nxp.com>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
	Stephen Boyd <sboyd@kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH] opp: Don't always remove static OPPs in _of_add_opp_table_v1()
Date: Thu, 15 Oct 2020 10:01:03 +0530	[thread overview]
Message-ID: <20201015043103.m6ghom52sqssh24z@vireshk-i7> (raw)
In-Reply-To: <AM6PR04MB496659599D41F6B88036420680020@AM6PR04MB4966.eurprd04.prod.outlook.com>

On 15-10-20, 02:35, Aisheng Dong wrote:
> Hi Viresh
> 
> Thanks for the quick fix.
> 
> > From: Viresh Kumar <viresh.kumar@linaro.org>
> > Sent: Wednesday, October 14, 2020 12:26 PM
> > 
> > The patch missed returning 0 early in case of success and hence the static OPPs
> > got removed by mistake. Fix it.
> > 
> > Fixes: 90d46d71cce2 ("opp: Handle multiple calls for same OPP table in
> > _of_add_opp_table_v1()")
> > Reported-by: Aisheng Dong <aisheng.dong@nxp.com>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> 
> Tested-by: Dong Aisheng <aisheng.dong@nxp.com>

Thanks.

Rafael: Please apply this one directly for 5.10-rc. Thanks.

-- 
viresh

  reply	other threads:[~2020-10-15  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14  4:26 [PATCH] opp: Don't always remove static OPPs in _of_add_opp_table_v1() Viresh Kumar
2020-10-15  2:35 ` Aisheng Dong
2020-10-15  4:31   ` Viresh Kumar [this message]
2020-10-20  5:28     ` Viresh Kumar
2020-10-28  9:53 ` Geert Uytterhoeven

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=20201015043103.m6ghom52sqssh24z@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=aisheng.dong@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vireshk@kernel.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 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.