xtensa: fix stack dump output
authorMax Filippov <jcmvbkbc@gmail.com>
Fri, 31 Mar 2017 22:58:40 +0000 (15:58 -0700)
committerMax Filippov <jcmvbkbc@gmail.com>
Fri, 31 Mar 2017 22:58:40 +0000 (15:58 -0700)
commite640cc306388b6f9dc8109d5c5d0550d7e69e5f7
treec8c4192218454002a02db69a15fac339065654ae
parent2b83878dd74a7c73bedcb6600663c1c46836e8af
xtensa: fix stack dump output

Use %pB in pr_cont format string instead of calling print_symbol
separately. It turns

  [   19.166249] Call Trace:
  [   19.167265]  [<a000e50a>]
  [   19.167843]  __warn+0x92/0xa0
  [   19.169656]  [<a000e554>]
  [   19.170059]  warn_slowpath_fmt+0x3c/0x40
  [   19.171934]  [<a02d5bd8>]

back into

  [   18.123240] Call Trace:
  [   18.125039]  [<a000e4f6>] __warn+0x92/0xa0
  [   18.126961]  [<a000e540>] warn_slowpath_fmt+0x3c/0x40

Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
arch/xtensa/kernel/traps.c