summaryrefslogtreecommitdiff
path: root/net/bluetooth
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavoars@kernel.org>2020-08-31 16:25:42 +0300
committerGustavo A. R. Silva <gustavoars@kernel.org>2020-10-30 01:22:59 +0300
commitb08eadd2726356eb4867397fafd046d2b8aad4bf (patch)
tree210504042119fff96c520bef8546354ddcb1f3a8 /net/bluetooth
parentfa29c9c11d4e2ba514421758991e5b3095642844 (diff)
downloadlinux-b08eadd2726356eb4867397fafd046d2b8aad4bf.tar.xz
Bluetooth: 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://www.kernel.org/doc/html/v5.9-rc1/process/deprecated.html#zero-length-and-one-element-arrays Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
Diffstat (limited to 'net/bluetooth')
-rw-r--r--net/bluetooth/msft.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/net/bluetooth/msft.c b/net/bluetooth/msft.c
index 8579bfeb2836..4b39534a14a1 100644
--- a/net/bluetooth/msft.c
+++ b/net/bluetooth/msft.c
@@ -12,12 +12,13 @@
struct msft_cp_read_supported_features {
__u8 sub_opcode;
} __packed;
+
struct msft_rp_read_supported_features {
__u8 status;
__u8 sub_opcode;
__le64 features;
__u8 evt_prefix_len;
- __u8 evt_prefix[0];
+ __u8 evt_prefix[];
} __packed;
struct msft_data {