unicore32/stacktrace: Remove the pointless ULONG_MAX marker
authorThomas Gleixner <tglx@linutronix.de>
Wed, 10 Apr 2019 10:27:59 +0000 (12:27 +0200)
committerThomas Gleixner <tglx@linutronix.de>
Sun, 14 Apr 2019 17:58:28 +0000 (19:58 +0200)
commitf8a9a269c28ddd5d741e747ceca753af01c828f2
tree6825f8abb8cc6cd8655c8338bf02df0e4f8afd50
parentb01f6d368d296cac099383a3eb200e135420f885
unicore32/stacktrace: Remove the pointless ULONG_MAX marker

Terminating the last trace entry with ULONG_MAX is a completely pointless
exercise and none of the consumers can rely on it because it's
inconsistently implemented across architectures. In fact quite some of the
callers remove the entry and adjust stack_trace.nr_entries afterwards.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Alexander Potapenko <glider@google.com>
Cc: Guan Xuetao <gxt@pku.edu.cn>
Link: https://lkml.kernel.org/r/20190410103644.036077691@linutronix.de
arch/unicore32/kernel/stacktrace.c