All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v14 1/9] firmware: qcom_scm: ipq5332: add support to pass metadata size
Date: Mon, 03 Aug 2026 10:55:43 +0000	[thread overview]
Message-ID: <20260803105544.54D9E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260803-rproc-v14-1-a1f87b0b0ad2@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The format specifier `%pe` is used with `PTR_ERR(gunyah_wdt_dev)`, causing a variadic type mismatch since `%pe` expects a pointer while `PTR_ERR()` returns a `long`.
--

--- Patch [1]: [PATCH v14 1/9] firmware: qcom_scm: ipq5332: add support to pass metadata size ---
commit fc14da7f3ebc47ea633f966df3048e0592f524ee
Author: Manikanta Mylavarapu <manikanta.mylavarapu@oss.qualcomm.com>

firmware: qcom_scm: ipq5332: add support to pass metadata size

IPQ5332 security software running under trustzone requires metadata size.
With new command support added in TrustZone that includes a size parameter,
this passes the metadata size as well.

> diff --git a/drivers/firmware/qcom/qcom_scm.c b/drivers/firmware/qcom/qcom_scm.c
> index 3eaa4c9ccf3cc..8902c445cf19f 100644
> --- a/drivers/firmware/qcom/qcom_scm.c
> +++ b/drivers/firmware/qcom/qcom_scm.c
[ ... ]
> @@ -2528,7 +2536,7 @@ static void qcom_scm_gunyah_wdt_init(struct qcom_scm *scm)
>  	gunyah_wdt_dev = platform_device_register_simple("gunyah-wdt", -1,
>  							 NULL, 0);
>  	if (IS_ERR(gunyah_wdt_dev)) {
> -		dev_err(scm->dev, "Failed to register Gunyah watchdog device: %ld\n",
> +		dev_err(scm->dev, "Failed to register Gunyah watchdog device: %pe\n",
>  			PTR_ERR(gunyah_wdt_dev));

[Severity: Medium]
Will this type mismatch cause formatting or build issues?

The %pe format specifier strictly expects a pointer, but PTR_ERR() returns a
long. Passing a long to %pe violates C variadic argument typing rules and
triggers a compiler warning that could break the build in configurations
using -Werror. At runtime, accessing a long as a pointer from va_list can
lead to undefined behavior depending on the architecture's calling
convention.

Could PTR_ERR() be removed so that gunyah_wdt_dev is passed directly to %pe?

>  		return;
>  	}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260803-rproc-v14-0-a1f87b0b0ad2@oss.qualcomm.com?part=1

  reply	other threads:[~2026-08-03 10:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 10:46 [PATCH v14 0/9] Add new driver for WCSS secure PIL loading Varadarajan Narayanan
2026-08-03 10:46 ` [PATCH v14 1/9] firmware: qcom_scm: ipq5332: add support to pass metadata size Varadarajan Narayanan
2026-08-03 10:55   ` sashiko-bot [this message]
2026-08-03 12:35   ` Mukesh Ojha
2026-08-04 11:23     ` Varadarajan Narayanan
2026-08-04 13:17       ` Mukesh Ojha
2026-08-04 17:38       ` Jeff Johnson
2026-08-03 10:46 ` [PATCH v14 2/9] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Varadarajan Narayanan
2026-08-03 11:01   ` sashiko-bot
2026-08-03 10:46 ` [PATCH v14 3/9] remoteproc: qcom: add hexagon based WCSS secure PIL driver Varadarajan Narayanan
2026-08-03 11:06   ` sashiko-bot
2026-08-03 12:44   ` Mukesh Ojha
2026-08-04 11:19     ` Vignesh Viswanathan
2026-08-04 13:10       ` Mukesh Ojha
2026-08-03 10:46 ` [PATCH v14 4/9] arm64: dts: qcom: ipq5018: add nodes to bring up q6 Varadarajan Narayanan
2026-08-03 10:46 ` [PATCH v14 5/9] arm64: dts: qcom: ipq5332: " Varadarajan Narayanan
2026-08-03 10:46 ` [PATCH v14 6/9] arm64: dts: qcom: ipq9574: " Varadarajan Narayanan
2026-08-03 10:46 ` [PATCH v14 7/9] arm64: dts: qcom: ipq5018: Enable q6v5_wcss Varadarajan Narayanan
2026-08-03 10:46 ` [PATCH v14 8/9] arm64: dts: qcom: ipq5332: " Varadarajan Narayanan
2026-08-03 10:46 ` [PATCH v14 9/9] arm64: dts: qcom: ipq9574: " Varadarajan Narayanan

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=20260803105544.54D9E1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=varadarajan.narayanan@oss.qualcomm.com \
    /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.