diff options
| author | 2019-07-19 12:18:46 -0700 | |
|---|---|---|
| committer | 2019-07-19 12:18:46 -0700 | |
| commit | 41ba485ef1d0dca98c5b194b8fb19201e123a08d (patch) | |
| tree | 93ce1d469c10db1662e3da3e7dd92c892ed1f390 /drivers/crypto/stm32/stm32-hash.c | |
| parent | Merge tag 'csky-for-linus-5.3-rc1' of git://github.com/c-sky/csky-linux (diff) | |
| parent | tracing: Fix user stack trace "??" output (diff) | |
| download | wireguard-linux-41ba485ef1d0dca98c5b194b8fb19201e123a08d.tar.xz wireguard-linux-41ba485ef1d0dca98c5b194b8fb19201e123a08d.zip | |
Merge tag 'trace-v5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fix from Steven Rostedt:
"Eiichi Tsukata found a small bug from the fixup of the stack code
Removing ULONG_MAX as the marker for the user stack trace end, made
the tracing code not know where the end is. The end is now marked with
a zero (NULL) pointer. Eiichi fixed this in the tracing code"
* tag 'trace-v5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
tracing: Fix user stack trace "??" output
Diffstat (limited to 'drivers/crypto/stm32/stm32-hash.c')
0 files changed, 0 insertions, 0 deletions
