diff options
author | John Hubbard <jhubbard@nvidia.com> | 2024-05-03 06:51:04 +0300 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2024-05-03 22:06:09 +0300 |
commit | 3309ca6f47f11b5d817ce1e5d8b2f1637b93243e (patch) | |
tree | 81ebada5f553959ff142e43e715887ea22fe2a4c /scripts/generate_rust_analyzer.py | |
parent | 0515089418d064000b7f375257c10107d3ad0c7f (diff) | |
download | linux-3309ca6f47f11b5d817ce1e5d8b2f1637b93243e.tar.xz |
selftests/cgroup: cpu_hogger init: use {} instead of {NULL}
First of all, in order to build with clang at all, one must first apply
Valentin Obst's build fix for LLVM [1]. Once that is done, then when
building with clang, via:
make LLVM=1 -C tools/testing/selftests
...clang generates warning here, because struct cpu_hogger has multiple
fields, and the code is initializing an array of these structs, and it
is incorrect to specify a single NULL value as the initializer.
Fix this by initializing with {}, so that the compiler knows to use
default initializer values for all fields in each array entry.
[1] https://lore.kernel.org/all/20240329-selftests-libmk-llvm-rfc-v1-1-2f9ed7d1c49f@valentinobst.de/
Signed-off-by: John Hubbard <jhubbard@nvidia.com>
Reviewed-by: Roman Gushchin <roman.gushchin@linux.dev>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions