From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>,
quic_yabdulra@quicinc.com, quic_carlv@quicinc.com
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] accel/qaic: Change aic100_image_table definition
Date: Tue, 7 Jan 2025 11:55:05 +0100 [thread overview]
Message-ID: <7bd9c6f6-a0c2-46ed-a06f-fe386cedc644@linux.intel.com> (raw)
In-Reply-To: <20241213185110.2469159-1-quic_jhugo@quicinc.com>
Reviewed-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
On 12/13/2024 7:51 PM, Jeffrey Hugo wrote:
> From: Youssef Samir <quic_yabdulra@quicinc.com>
>
> aic100_image_table is currently defined as a "const char *" array,
> this can potentially lead to the accidental modification of the
> pointers inside. Also, checkpatch.pl gives a warning about it.
>
> Change the type to a "const char * const" array to make the pointers
> immutable, preventing accidental modification of the images' paths.
>
> Signed-off-by: Youssef Samir <quic_yabdulra@quicinc.com>
> Reviewed-by: Carl Vanderlip <quic_carlv@quicinc.com>
> Reviewed-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> ---
> drivers/accel/qaic/sahara.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/accel/qaic/sahara.c b/drivers/accel/qaic/sahara.c
> index 21d58aed0deb..09c8b055aa81 100644
> --- a/drivers/accel/qaic/sahara.c
> +++ b/drivers/accel/qaic/sahara.c
> @@ -160,7 +160,7 @@ struct sahara_context {
> struct work_struct fw_work;
> struct work_struct dump_work;
> struct mhi_device *mhi_dev;
> - const char **image_table;
> + const char * const *image_table;
> u32 table_size;
> u32 active_image_id;
> const struct firmware *firmware;
> @@ -177,7 +177,7 @@ struct sahara_context {
> bool is_mem_dump_mode;
> };
>
> -static const char *aic100_image_table[] = {
> +static const char * const aic100_image_table[] = {
> [1] = "qcom/aic100/fw1.bin",
> [2] = "qcom/aic100/fw2.bin",
> [4] = "qcom/aic100/fw4.bin",
next prev parent reply other threads:[~2025-01-07 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 18:51 [PATCH] accel/qaic: Change aic100_image_table definition Jeffrey Hugo
2025-01-07 10:55 ` Jacek Lawrynowicz [this message]
2025-01-17 16:05 ` Jeffrey Hugo
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=7bd9c6f6-a0c2-46ed-a06f-fe386cedc644@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_yabdulra@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox