summaryrefslogtreecommitdiffstats
path: root/drivers/thunderbolt
diff options
context:
space:
mode:
authorGustavo A. R. Silva2019-06-23 08:33:21 +0200
committerDmitry Torokhov2019-06-23 08:34:57 +0200
commit3d4149ec87fdab5006cb94f8ebe4720b1ee7e564 (patch)
tree64c627ea8d660036d6a2de14696c5bc83a05fa8c /drivers/thunderbolt
parentInput: tca8418 - remove set but not used variable 'max_keys' (diff)
downloadkernel-qcow2-linux-3d4149ec87fdab5006cb94f8ebe4720b1ee7e564.tar.gz
kernel-qcow2-linux-3d4149ec87fdab5006cb94f8ebe4720b1ee7e564.tar.xz
kernel-qcow2-linux-3d4149ec87fdab5006cb94f8ebe4720b1ee7e564.zip
Input: gpio_keys_polled - use struct_size() in devm_kzalloc()
One of the more common cases of allocation size calculations is finding the size of a structure that has a zero-sized array at the end, along with memory for some number of elements for that array. For example: struct gpio_keys_polled_dev { ... struct gpio_keys_button_data data[0]; }; size = sizeof(struct gpio_keys_polled_dev) + count * sizeof(struct gpio_keys_button_data); instance = devm_kzalloc(dev, size, GFP_KERNEL); Instead of leaving these open-coded and prone to type mistakes, we can now use the new struct_size() helper: instance = devm_kzalloc(dev, struct_size(instance, data, count), GFP_KERNEL); Notice that, in this case, variable size is not necessary, hence it is removed. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/thunderbolt')
0 files changed, 0 insertions, 0 deletions