All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] cpufreq: qcom-hw: drop devm_xxx() calls from init/exit hooks
Date: Mon, 01 Mar 2021 19:59:43 +0000	[thread overview]
Message-ID: <161462878316.6187.10719360431050184498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210119023925.22724-1-shawn.guo@linaro.org>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Tue, 19 Jan 2021 10:39:25 +0800 you wrote:
> Commit f17b3e44320b ("cpufreq: qcom-hw: Use
> devm_platform_ioremap_resource() to simplify code") introduces
> a regression on platforms using the driver, by failing to initialise
> a policy, when one is created post hotplug.
> 
> When all the CPUs of a policy are hoptplugged out, the call to .exit()
> and later to devm_iounmap() does not release the memory region that was
> requested during devm_platform_ioremap_resource().  Therefore,
> a subsequent call to .init() will result in the following error, which
> will prevent a new policy to be initialised:
> 
> [...]

Here is the summary with links:
  - [v2] cpufreq: qcom-hw: drop devm_xxx() calls from init/exit hooks
    https://git.kernel.org/qcom/c/67fc209b527d

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-03-01 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  2:39 [PATCH v2] cpufreq: qcom-hw: drop devm_xxx() calls from init/exit hooks Shawn Guo
2021-02-18  3:19 ` Shawn Guo
2021-02-18  9:01   ` Viresh Kumar
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [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=161462878316.6187.10719360431050184498.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=shawn.guo@linaro.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.