summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorNihar Chaithanya <niharchaithanya@gmail.com>2024-10-11 14:45:38 +0300
committerAndrew Morton <akpm@linux-foundation.org>2025-01-14 09:40:42 +0300
commit5f1c8108e7ad510456733d143b8ffc4e2408b1a1 (patch)
treea75af919993c991c8f9c82134b13c10c1fb65bd0 /tools/perf/scripts/python
parent21641bd9a7a7ce0360106a5a8e5b89a4fc74529d (diff)
downloadlinux-5f1c8108e7ad510456733d143b8ffc4e2408b1a1.tar.xz
mm:kasan: fix sparse warnings: Should it be static?
Yes, when making the global variables kasan_ptr_result and kasan_int_result as static volatile, the warnings are removed and the variable and assignments are retained, but when just static is used I understand that it might be optimized. Add a fix making the global varaibles - static volatile, removing the warnings: mm/kasan/kasan_test.c:36:6: warning: symbol 'kasan_ptr_result' was not declared. Should it be static? mm/kasan/kasan_test.c:37:5: warning: symbol 'kasan_int_result' was not declared. Should it be static? Link: https://lkml.kernel.org/r/20241011114537.35664-1-niharchaithanya@gmail.com Reported-by: kernel test robot <lkp@intel.com> Closes: https://lore.kernel.org/oe-kbuild-all/202312261010.o0lRiI9b-lkp@intel.com/ Signed-off-by: Nihar Chaithanya <niharchaithanya@gmail.com> Reviewed-by: Dmitry Vyukov <dvyukov@google.com> Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com> Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com> Cc: Shuah Khan <skhan@linuxfoundation.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions