diff options
| author | Randall Spangler <rspangler@chromium.org> | 2017-10-30 15:43:17 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2017-11-12 10:49:49 -0800 |
| commit | ff82ffb0a9cd28bc186eef2e86cfc61aec2d6029 (patch) | |
| tree | 7b3968a64914817186df868a3caf2bb174c24c08 /firmware/lib/vboot_ui_menu.c | |
| parent | db79418605d6c128a03af99156467963c01c05d8 (diff) | |
| download | vboot-ff82ffb0a9cd28bc186eef2e86cfc61aec2d6029.tar.gz | |
vboot: use VBNV_ constants with VbNvGet()
The vboot1 library VbNvGet() / VbNvSet() functions use enum VbNvParam
(VBNV_*) constants.
The vboot2 library vb2_nv_get() / vb2_nv_set() functions use enum
vb2_nv_param constants.
Do not mix the two. In the one instance where this happens in the
current code, we get lucky, because VBNV_DEV_BOOT_FASTBOOT_FULL_CAP
and VB2_NV_DEV_BOOT_FASTBOOT_FULL_CAP evaluate to the same value, so
this was harmless. But fix that now so nobody else copy/pastes that
pattern for a param where this isn't true.
BUG=none
BRANCH=none
TEST=make runtests
Change-Id: I1facbe1d97591dc8b1e6b38717924b884949da57
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/764970
Reviewed-by: Julius Werner <jwerner@chromium.org>
Diffstat (limited to 'firmware/lib/vboot_ui_menu.c')
0 files changed, 0 insertions, 0 deletions