From: patchwork-bot+linux-arm-msm@kernel.org
To: David Collins <collinsd@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] regulator: core: avoid regulator_resolve_supply() race condition
Date: Mon, 01 Mar 2021 19:59:44 +0000 [thread overview]
Message-ID: <161462878469.6187.16660630649236656657.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1610068562-4410-1-git-send-email-collinsd@codeaurora.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Thu, 7 Jan 2021 17:16:02 -0800 you wrote:
> The final step in regulator_register() is to call
> regulator_resolve_supply() for each registered regulator
> (including the one in the process of being registered). The
> regulator_resolve_supply() function first checks if rdev->supply
> is NULL, then it performs various steps to try to find the supply.
> If successful, rdev->supply is set inside of set_supply().
>
> [...]
Here is the summary with links:
- regulator: core: avoid regulator_resolve_supply() race condition
https://git.kernel.org/qcom/c/eaa7995c529b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-01 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 1:16 [PATCH] regulator: core: avoid regulator_resolve_supply() race condition David Collins
2021-01-11 16:28 ` Mark Brown
[not found] ` <CGME20210112213419eucas1p24231e4d0ac11c31184f2f8f3f20cbd9d@eucas1p2.samsung.com>
2021-01-12 21:34 ` Marek Szyprowski
2021-01-18 11:41 ` Naresh Kamboju
2021-01-18 20:49 ` Mark Brown
2021-01-21 9:41 ` Marek Szyprowski
2021-01-21 15:44 ` Mark Brown
2021-01-21 20:30 ` Marek Szyprowski
2021-01-23 1:54 ` David Collins
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=161462878469.6187.16660630649236656657.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=collinsd@codeaurora.org \
--cc=linux-arm-msm@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).