summaryrefslogtreecommitdiff
path: root/src/mainboard/google/octopus/mainboard.c
diff options
context:
space:
mode:
authorYu-Ping Wu <yupingso@chromium.org>2021-04-15 10:06:27 +0800
committerPatrick Georgi <pgeorgi@google.com>2021-04-16 06:42:25 +0000
commitba49444c336b8207bc055a73ee860d056aef46d4 (patch)
tree51360f907c35409d20f536e5b704af65679839fc /src/mainboard/google/octopus/mainboard.c
parent46ca25d8c9099d3ef32f8cb76ba2d45be60fc24e (diff)
soc/mediatek: Remove misleading memory logs
When MRC cache region type is not found (for example, in recovery mode with !HAS_RECOVERY_MRC_CACHE), mrc_cache_stash_data() will return 0. Therefore, the platform code is not able to tell from the return value if the MRC cache data is actually written to flash or not. Since the MRC driver is already pretty verbose, ignore the return value and remove the misleading memory logs. BUG=none TEST=emerge-asurada coreboot BRANCH=asurada Change-Id: I6b411664ca91b9be2d4518a09e9734d26db02d6e Signed-off-by: Yu-Ping Wu <yupingso@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/52361 Reviewed-by: Hung-Te Lin <hungte@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/google/octopus/mainboard.c')
0 files changed, 0 insertions, 0 deletions