All of lore.kernel.org
 help / color / mirror / Atom feed
From: JeffyChen <jeffy.chen@rock-chips.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	linux-clk@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	lkft-triage@lists.linaro.org,
	Anders Roxell <anders.roxell@linaro.org>,
	mturquette@baylibre.com,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Basil Eljuse <Basil.Eljuse@arm.com>
Subject: Re: WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:4156 __clk_put+0xfc/0x130
Date: Tue, 17 Mar 2020 08:18:10 +0800	[thread overview]
Message-ID: <5E701742.60706@rock-chips.com> (raw)
In-Reply-To: <158438237211.88485.8872594504996170580@swboyd.mtv.corp.google.com>

Hi Stephen,

On 03/17/2020 02:12 AM, Stephen Boyd wrote:
> Looks like Greg picked up this patch[1] as commit b8fe128dad8f
> ("arch_topology: Adjust initial CPU capacities with current freq") from
> the list. Not sure it's correct though and I haven't looked in any more
> detail. At least, not calling clk_put() unless it is a valid pointer
> will work to quiet this warning.
>
> [1] https://lore.kernel.org/r/20200113034815.25924-1-jeffy.chen@rock-chips.com
>

Sorry, i made a stupid mistake... Sending the fix now, thanks for 
checking that.



      reply	other threads:[~2020-03-17  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  9:05 WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:4156 __clk_put+0xfc/0x130 Naresh Kamboju
2020-03-16 18:12 ` Stephen Boyd
2020-03-17  0:18   ` JeffyChen [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=5E701742.60706@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=Basil.Eljuse@arm.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=mturquette@baylibre.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=sboyd@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.