From: Ricardo Ribalda <ribalda@chromium.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Vikash Garodia <quic_vgarodia@quicinc.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Ricardo Ribalda <ribalda@chromium.org>
Subject: [PATCH v4 11/11] media: venus: Refactor hfi_buffer_alloc_mode_supported
Date: Thu, 06 Jun 2024 13:16:45 +0000 [thread overview]
Message-ID: <20240606-cocci-flexarray-v4-11-3379ee5eed28@chromium.org> (raw)
In-Reply-To: <20240606-cocci-flexarray-v4-0-3379ee5eed28@chromium.org>
Replace the old style single element array at the end of the struct with
a flex array.
The code does not allocate this structure, so the size change should not
be a problem.
This fixes the following cocci warning:
drivers/media/platform/qcom/venus/hfi_helper.h:1233:5-9: WARNING use flexible-array member instead (https://www.kernel.org/doc/html/latest/process/deprecated.html#zero-length-and-one-element-arrays)
Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
---
drivers/media/platform/qcom/venus/hfi_helper.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/qcom/venus/hfi_helper.h b/drivers/media/platform/qcom/venus/hfi_helper.h
index dee439ea4d2e..9545c964a428 100644
--- a/drivers/media/platform/qcom/venus/hfi_helper.h
+++ b/drivers/media/platform/qcom/venus/hfi_helper.h
@@ -1230,7 +1230,7 @@ struct hfi_interlace_format_supported {
struct hfi_buffer_alloc_mode_supported {
u32 buffer_type;
u32 num_entries;
- u32 data[1];
+ u32 data[];
};
struct hfi_metadata_pass_through {
--
2.45.2.505.gda0bf45e8d-goog
prev parent reply other threads:[~2024-06-06 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 13:16 [PATCH v4 00/11] media: Fix the last set of coccinelle warnings Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 01/11] media: dvb-frontend/mxl5xx: Refactor struct MBIN_FILE_T and MBIN_SEGMENT_T Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 02/11] media: venus: Remove unused structs Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 03/11] media: venus: Use flex array for hfi_session_release_buffer_pkt Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 04/11] media: venus: Refactor struct hfi_uncompressed_plane_info Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 05/11] media: venus: Refactor struct hfi_session_get_property_pkt Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 06/11] media: venus: Refactor struct hfi_uncompressed_format_supported Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 07/11] media: venus: Refactor hfi_session_empty_buffer_uncompressed_plane0_pkt Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 08/11] media: venus: Refactor hfi_session_empty_buffer_compressed_pkt Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 09/11] media: venus: Refactor hfi_sys_get_property_pkt Ricardo Ribalda
2024-06-06 13:16 ` [PATCH v4 10/11] media: venus: Refactor hfi_session_fill_buffer_pkt Ricardo Ribalda
2024-06-06 13:16 ` Ricardo Ribalda [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=20240606-cocci-flexarray-v4-11-3379ee5eed28@chromium.org \
--to=ribalda@chromium.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_vgarodia@quicinc.com \
--cc=stanimir.k.varbanov@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).