diff options
| author | Qianfeng Rong <rongqianfeng@vivo.com> | 2025-09-07 17:35:57 +0800 |
|---|---|---|
| committer | Hans Verkuil <hverkuil+cisco@kernel.org> | 2026-01-05 15:56:31 +0100 |
| commit | e4f63453fd37d79501676c6f32790179909b5042 (patch) | |
| tree | a6ddc8efd3eb05ac19c5c3387ab169ee7ad4ddb2 /tools/perf/scripts/python | |
| parent | 88e935de7cf8795d7a6a51385db87ecb361a7050 (diff) | |
| download | linux-e4f63453fd37d79501676c6f32790179909b5042.tar.gz linux-e4f63453fd37d79501676c6f32790179909b5042.zip | |
media: mediatek: vcodec: use = { } instead of memset()
Based on testing and recommendations by David Lechner et al. [1][2],
using = { } to initialize a structure or array is the preferred way
to do this in the kernel.
Converts memset() to = { }, thereby:
- Eliminating the risk of sizeof() mismatches.
- Simplifying the code.
[1]: https://lore.kernel.org/linux-iio/202505090942.48EBF01B@keescook/
[2]: https://lore.kernel.org/lkml/20250614151844.50524610@jic23-huawei/
Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil+cisco@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions