mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-14 15:54:15 +08:00
a67012412e
And that I didn't have the bad code in my config file when I cross compiled it, although there are a few other errors in sh that makes it not build for me, I missed that I added one more. I replaced WARN_ON(current->curr_ret_stack) with WARN_ON(ftrace_graph_get_ret_stack(current, 1) where it should be: WARN_ON(ftrace_graph_get_ret_stack(current, 1)) -----BEGIN PGP SIGNATURE----- iIoEABYIADIWIQRRSw7ePDh/lE+zeZMp5XQQmuv6qgUCXC7PuRQccm9zdGVkdEBn b29kbWlzLm9yZwAKCRAp5XQQmuv6qv7rAQDMtgYCknUW6P5TOgytQ9x7+TfMld1O mqD689wl9Rb5GwD/ec9BsDoSu7jeVizb7Si1kUAPYndV4E/3NFbwSZbaqAU= =W7wU -----END PGP SIGNATURE----- Merge tag 'trace-v4.21-1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace Pull ftrace sh build fix from Steven Rostedt: "It appears that the zero-day bot did find a bug in my sh build. And that I didn't have the bad code in my config file when I cross compiled it, although there are a few other errors in sh that makes it not build for me, I missed that I added one more" * tag 'trace-v4.21-1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: sh: ftrace: Fix missing parenthesis in WARN_ON() |
||
---|---|---|
.. | ||
boards | ||
boot | ||
cchips | ||
configs | ||
drivers | ||
include | ||
kernel | ||
lib | ||
lib64 | ||
math-emu | ||
mm | ||
oprofile | ||
tools | ||
Kconfig | ||
Kconfig.cpu | ||
Kconfig.debug | ||
Makefile |