summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 5d6c61a)
raw | patch | inline | side by side (parent: 5d6c61a)
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) |
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>
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 | patch | blob | history |
diff --git a/common/board_f.c b/common/board_f.c
index 213d0440667f871812d039ba03061058662bebc4..96503ff8d3c36a12339de06b0f872f678118baec 100644 (file)
--- a/common/board_f.c
+++ b/common/board_f.c
return ret;
}
- printf("%s", desc);
+ printf("CPU: %s\n", desc);
return 0;
}