From: patchwork-bot+linux-amlogic@kernel.org
To: Jianxin Pan <jianxin.pan@amlogic.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH] soc: amlogic: fix compile failure with MESON_SECURE_PM_DOMAINS & !MESON_SM
Date: Sat, 29 Feb 2020 18:21:48 +0000 [thread overview]
Message-ID: <158300050888.2726.12421973865801415332.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1581955933-69832-1-git-send-email-jianxin.pan@amlogic.com>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Tue, 18 Feb 2020 00:12:13 +0800 you wrote:
> When MESON_SECURE_PM_DOMAINS & !MESON_SM, there will be compile failure:
> .../meson-secure-pwrc.o: In function `meson_secure_pwrc_on':
> .../meson-secure-pwrc.c:76: undefined reference to `meson_sm_call'
>
> Fix this by adding depends on MESON_SM for MESON_SECURE_PM_DOMAINS.
>
> Fixes: b3dde5013e13 ("soc: amlogic: Add support for Secure power domains controller")
>
> [...]
Here is a summary with links:
- soc: amlogic: fix compile failure with MESON_SECURE_PM_DOMAINS & !MESON_SM
https://git.kernel.org/khilman/linux-amlogic/c/9ef7a7920678b10431d88635f9a4a49bd23ca3a7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-02-29 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:12 [PATCH] soc: amlogic: fix compile failure with MESON_SECURE_PM_DOMAINS & !MESON_SM Jianxin Pan
2020-02-17 21:07 ` Stephen Rothwell
2020-02-17 22:22 ` Stephen Rothwell
2020-02-23 23:16 ` Stephen Rothwell
2020-02-29 16:55 ` Kevin Hilman
2020-03-01 0:47 ` Stephen Rothwell
2020-02-29 18:21 ` patchwork-bot+linux-amlogic [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=158300050888.2726.12421973865801415332.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=jianxin.pan@amlogic.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.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).