From: patchwork-bot+linux-arm-msm@kernel.org
To: John Stultz <john.stultz@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] regulator: Kconfig: Fix REGULATOR_QCOM_RPMH dependencies to avoid build error
Date: Tue, 29 Dec 2020 20:15:34 +0000 [thread overview]
Message-ID: <160927293411.13751.17469569345837308390.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201123222359.103822-1-john.stultz@linaro.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Mon, 23 Nov 2020 22:23:59 +0000 you wrote:
> The kernel test robot reported the following build error:
>
> All errors (new ones prefixed by >>):
>
> xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_vrm_get_voltage_sel':
> qcom-rpmh-regulator.c:(.text+0x270): undefined reference to `rpmh_write'
> xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_send_request':
> qcom-rpmh-regulator.c:(.text+0x2f2): undefined reference to `rpmh_write'
> xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_vrm_get_voltage_sel':
> >> qcom-rpmh-regulator.c:(.text+0x274): undefined reference to `rpmh_write_async'
> xtensa-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_send_request':
> qcom-rpmh-regulator.c:(.text+0x2fc): undefined reference to `rpmh_write_async'
>
> [...]
Here is the summary with links:
- [v2] regulator: Kconfig: Fix REGULATOR_QCOM_RPMH dependencies to avoid build error
https://git.kernel.org/qcom/c/34c5aa2666db
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:[~2020-12-29 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 22:23 [PATCH v2] regulator: Kconfig: Fix REGULATOR_QCOM_RPMH dependencies to avoid build error John Stultz
2020-11-24 4:51 ` Bjorn Andersson
2020-11-24 15:37 ` Mark Brown
2020-12-29 20:15 ` 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=160927293411.13751.17469569345837308390.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=john.stultz@linaro.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 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.