summaryrefslogtreecommitdiffstats
path: root/drivers/firmware/google
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2020-02-21 09:30:21 -0600
committerGustavo A. R. Silva <gustavoars@kernel.org>2020-06-15 23:08:16 -0500
commitea9ee9976750b3d047141ebeb12ba92b634dfbef (patch)
tree5d232774f2ae17fe089ea783c52e1e496dd8ba39 /drivers/firmware/google
parent8e849a41276a5bae6050d89ed9421bd882c77d2e (diff)
downloadlinux-ea9ee9976750b3d047141ebeb12ba92b634dfbef.tar.bz2
firmware: google: memconsole: 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>
Diffstat (limited to 'drivers/firmware/google')
-rw-r--r--drivers/firmware/google/memconsole-coreboot.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/firmware/google/memconsole-coreboot.c b/drivers/firmware/google/memconsole-coreboot.c
index fd7f0fbec07e..d17e4d6ac9bc 100644
--- a/drivers/firmware/google/memconsole-coreboot.c
+++ b/drivers/firmware/google/memconsole-coreboot.c
@@ -21,7 +21,7 @@
struct cbmem_cons {
u32 size_dont_access_after_boot;
u32 cursor;
- u8 body[0];
+ u8 body[];
} __packed;
#define CURSOR_MASK ((1 << 28) - 1)