summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2020-02-21 16:32:33 +0100
committerGustavo A. R. Silva <gustavoars@kernel.org>2020-06-16 06:08:21 +0200
commitaa125f313d8e7d04bf001175dadeabaf8723c00b (patch)
treec0cfaac53c1fecbd89ef6b6c57ad332618aa6691
parentfirmware: google: memconsole: Replace zero-length array with flexible-array m... (diff)
downloadlinux-aa125f313d8e7d04bf001175dadeabaf8723c00b.tar.xz
linux-aa125f313d8e7d04bf001175dadeabaf8723c00b.zip
firmware: google: vpd: Replace zero-length array with flexible-array member
There is a regular need in the kernel to provide a way to declare having a dynamically sized set of trailing elements in a structure. Kernel code should always use “flexible array members”[1] for these cases. The older style of one-element or zero-length arrays should no longer be used[2]. [1] https://en.wikipedia.org/wiki/Flexible_array_member [2] https://github.com/KSPP/linux/issues/21 Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
-rw-r--r--drivers/firmware/google/vpd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/firmware/google/vpd.c b/drivers/firmware/google/vpd.c
index db0812263d46..d23c5c69ab52 100644
--- a/drivers/firmware/google/vpd.c
+++ b/drivers/firmware/google/vpd.c
@@ -32,7 +32,7 @@ struct vpd_cbmem {
u32 version;
u32 ro_size;
u32 rw_size;
- u8 blob[0];
+ u8 blob[];
};
struct vpd_section {