public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.Li@nxp.com>
To: Linus Walleij <linusw@kernel.org>,
	Bartosz Golaszewski <brgl@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Frank Li <Frank.Li@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	arnaud.pouliquen@foss.st.com
Cc: Frank Li <frank.li@nxp.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Shenwei Wang <shenwei.wang@nxp.com>, Peng Fan <peng.fan@nxp.com>,
	devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-imx@nxp.com
Subject: Re: [PATCH v9 4/5] gpio: rpmsg: add support for NXP legacy firmware protocol
Date: Thu,  5 Mar 2026 10:16:01 -0500	[thread overview]
Message-ID: <20260305151602.3913147-1-Frank.Li@nxp.com> (raw)
In-Reply-To: <20260304211808.1437846-5-shenwei.wang@nxp.com>

From: Frank Li (AI-BOT) <frank.li@nxp.com>


> +static int imx_std_cmd_map[] = {

AI: Should be 'static const int' since this is a read-only lookup table.

> +	if (msg->cmd >= sizeof(imx_std_cmd_map))

AI: Use ARRAY_SIZE(imx_std_cmd_map) instead of sizeof() for clarity.

because imx_std_cmd_map is array, AI most likely is correct.

Frank


  reply	other threads:[~2026-03-05 15:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 21:18 [PATCH v9 0/5] Enable Remote GPIO over RPMSG on i.MX Platform Shenwei Wang
2026-03-04 21:18 ` [PATCH v9 1/5] docs: driver-api: gpio: rpmsg gpio driver over rpmsg bus Shenwei Wang
2026-03-05  7:11   ` kernel test robot
2026-03-05 15:39   ` Daniel Baluta
2026-03-04 21:18 ` [PATCH v9 2/5] dt-bindings: remoteproc: imx_rproc: Add "rpmsg" subnode support Shenwei Wang
2026-03-04 21:18 ` [PATCH v9 3/5] gpio: rpmsg: add generic rpmsg GPIO driver Shenwei Wang
2026-03-04 21:18 ` [PATCH v9 4/5] gpio: rpmsg: add support for NXP legacy firmware protocol Shenwei Wang
2026-03-05 15:16   ` Frank Li [this message]
2026-03-06  7:35   ` Dan Carpenter
2026-03-06 14:24   ` Andrew Lunn
2026-03-06 16:34     ` Shenwei Wang
2026-03-06 16:56       ` Andrew Lunn
2026-03-04 21:18 ` [PATCH v9 5/5] arm64: dts: imx8ulp: Add rpmsg node under imx_rproc Shenwei Wang

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=20260305151602.3913147-1-Frank.Li@nxp.com \
    --to=frank.li@nxp.com \
    --cc=andersson@kernel.org \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shenwei.wang@nxp.com \
    --cc=skhan@linuxfoundation.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