diff options
| author | John Hubbard <jhubbard@nvidia.com> | 2023-06-06 00:16:29 -0700 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2023-06-19 16:19:01 -0700 |
| commit | b764253c18821da31c49a260f92f5d093cf1637e (patch) | |
| tree | c73c9b0bd2214a2d37aab6be8b466f4b6469360a /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 2f29d16c9d30357a27432e2b35fe70833b5c7762 (diff) | |
| download | linux-b764253c18821da31c49a260f92f5d093cf1637e.tar.gz linux-b764253c18821da31c49a260f92f5d093cf1637e.zip | |
selftests/mm: fix "warning: expression which evaluates to zero..." in mlock2-tests.c
The stop variable is a char*, and the code was assigning a char value to
it. This was generating a warning when compiling with clang.
However, as both David and Peter pointed out, stop is not even used
after the problematic assignment to a char type. So just delete that
line entirely.
Link: https://lkml.kernel.org/r/20230606071637.267103-4-jhubbard@nvidia.com
Signed-off-by: John Hubbard <jhubbard@nvidia.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Tested-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions