Thomas Gleixner fa9833992d riscv/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: linux-riscv@lists.infradead.org Cc: Palmer Dabbelt <palmer@sifive.com> Cc: Albert Ou <aou@eecs.berkeley.edu> Link: https://lkml.kernel.org/r/20190410103644.131061192@linutronix.de		2019-04-14 19:58:28 +02:00
..
boot	RISC-V: Build flat and compressed kernel images	2018-11-20 05:19:09 -08:00
configs	RISC-V: defconfig: Add CRYPTO_DEV_VIRTIO=y	2019-01-23 14:09:01 -08:00
include	Andy Lutomirski approached me to tell me that the syscall_get_arguments()	2019-04-05 13:15:57 -10:00
kernel	riscv/stacktrace: Remove the pointless ULONG_MAX marker	2019-04-14 19:58:28 +02:00
lib	RISC-V: lib: minor asm cleanup	2018-12-21 08:17:02 -08:00
mm	RISC-V: Always compile mm/init.c with cmodel=medany and notrace	2019-03-26 18:25:06 -07:00
net	bpf, riscv: add BPF JIT for RV64G	2019-02-05 16:56:10 +01:00
Kconfig	DMA mapping updates for 5.1	2019-03-10 11:54:48 -07:00
Kconfig.debug	RISC-V: Remove EARLY_PRINTK support	2018-12-17 10:23:46 -08:00
Makefile	bpf, riscv: add BPF JIT for RV64G	2019-02-05 16:56:10 +01:00