summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorMiguel Ojeda <ojeda@kernel.org>2025-01-12 18:29:45 +0300
committerJonathan Corbet <corbet@lwn.net>2025-01-13 20:46:22 +0300
commit25fb101385f7abf6d24ae92cd8f8c84882d1e942 (patch)
treed0b95b9f16318fe0ad856d32c3508aada7462ec7 /tools/perf/scripts/python/task-analyzer.py
parentcd9123eeb2245a1d63d3677118322bf2fc0d4a23 (diff)
downloadlinux-25fb101385f7abf6d24ae92cd8f8c84882d1e942.tar.xz
docs: submitting-patches: clarify difference between Acked-by and Reviewed-by
Newcomers to the kernel need to learn the different tags that are used in commit messages and when to apply them. Acked-by is sometimes misunderstood, since the documentation did not really clarify (up to the previous commit) when it should be used, especially compared to Reviewed-by. The previous commit already clarified who the usual providers of Acked-by tags are, with examples. Thus provide a clarification paragraph for the comparison with Reviewed-by, and give a couple examples reusing the cases given above, in the previous commit. Acked-by: Shuah Khan <skhan@linuxfoundation.org> Acked-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Miguel Ojeda <ojeda@kernel.org> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Acked-by: Krzysztof Kozlowski <krzk@kernel.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250112152946.761150-3-ojeda@kernel.org
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions