| author | Bin Meng <bmeng.cn@gmail.com> | |
| Thu, 11 Oct 2018 05:06:55 +0000 (22:06 -0700) | ||
| committer | Simon Glass <sjg@chromium.org> | |
| Wed, 14 Nov 2018 17:16:27 +0000 (09:16 -0800) | ||
| commit | ecfe66330d3093b701a26363470c0b6a32a02d89 | |
| tree | 458f490fb6c859e02ba11f68a81f2dfb84b133e1 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 5d6c61ac404c5c7c463ea6ee216145f29a603f60 | commit | diff |
dm: cpu: Fix print_cpuinfo() output
It was observed that current output of print_cpuinfo() on QEMU
x86 targets does not have an ending '\n', neither have a leading
'CPU:' any more. However it used to have these before.
It turns out commit c0434407b595 introduced a unified DM version
of print_cpuinfo() that exposed such issue on QEMU x86.
Fixes: c0434407b595 ("board_f: Use static print_cpuinfo if CONFIG_CPU is active")
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
It was observed that current output of print_cpuinfo() on QEMU
x86 targets does not have an ending '\n', neither have a leading
'CPU:' any more. However it used to have these before.
It turns out commit c0434407b595 introduced a unified DM version
of print_cpuinfo() that exposed such issue on QEMU x86.
Fixes: c0434407b595 ("board_f: Use static print_cpuinfo if CONFIG_CPU is active")
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
| common/board_f.c | diff | blob | history |