From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH master 1/2] remoteproc: stm32: fix typo in Kconfig symbol
Date: Mon, 23 Oct 2023 11:49:59 +0200 [thread overview]
Message-ID: <20231023094959.GR3359458@pengutronix.de> (raw)
In-Reply-To: <20231020133744.555063-1-a.fatoum@pengutronix.de>
On Fri, Oct 20, 2023 at 03:37:43PM +0200, Ahmad Fatoum wrote:
> The Kconfig symbol for enabling support for the ARM Secure Monitor Call
> Calling Convention if CONFIG_ARM_SMCCC and not CONFIG_ARM_SMCC, but the
> latter is checked with IS_ENABLED() in the driver. Fix the typo.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> drivers/remoteproc/stm32_rproc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks
Sascha
>
> diff --git a/drivers/remoteproc/stm32_rproc.c b/drivers/remoteproc/stm32_rproc.c
> index b6a62634842f..b2282f2fac5b 100644
> --- a/drivers/remoteproc/stm32_rproc.c
> +++ b/drivers/remoteproc/stm32_rproc.c
> @@ -56,7 +56,7 @@ static int stm32_rproc_set_hold_boot(struct rproc *rproc, bool hold)
>
> val = hold ? HOLD_BOOT : RELEASE_BOOT;
>
> - if (IS_ENABLED(CONFIG_ARM_SMCC) && ddata->secured_soc) {
> + if (IS_ENABLED(CONFIG_ARM_SMCCC) && ddata->secured_soc) {
> arm_smccc_smc(STM32_SMC_RCC, STM32_SMC_REG_WRITE,
> hold_boot->reg, val, 0, 0, 0, 0, &smc_res);
> err = smc_res.a0;
> --
> 2.39.2
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-10-23 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 13:37 Ahmad Fatoum
2023-10-20 13:37 ` [PATCH master 2/2] remoteproc: stm32: fix breakage after DT sync with upstream Ahmad Fatoum
2023-10-23 9:49 ` Sascha Hauer [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=20231023094959.GR3359458@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@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