diff options
| author | Randall Spangler <rspangler@chromium.org> | 2018-03-01 12:31:44 -0800 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-03-01 19:13:13 -0800 |
| commit | 68ca41067083ee78f5e6b96ba0e2ce9a76cecd3b (patch) | |
| tree | 91dabd15efc81e3f95d9a0150a8be9d91272c97d /tests | |
| parent | f35b63590adb5df9ca881d09d58735093962168d (diff) | |
| download | vboot-68ca41067083ee78f5e6b96ba0e2ce9a76cecd3b.tar.gz | |
firmware: Remove VbLockDevice()stabilize-10452.96.Bstabilize-10452.90.Bstabilize-10452.85.Bstabilize-10452.81.Brelease-R66-10452.B
VbLockDevice() would be inconvenient to port to 64-byte NV storage
records because it doesn't take VbSharedData flags or a vb2_context.
So, just have depthcharge call vbnv_write() directly (as it does in
other places in fastboot.c) and get rid of this API.
BUG=chromium:789276
BRANCH=none
TEST=make runtests
CQ-DEPEND=CL:944183
Change-Id: I2aeaecf7f929cd1a1ebd1f6850d0dd96c6fabb49
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/944243
Reviewed-by: Furquan Shaikh <furquan@chromium.org>
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/vboot_api_kernel6_tests.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/tests/vboot_api_kernel6_tests.c b/tests/vboot_api_kernel6_tests.c index 801ff727..c44c3c12 100644 --- a/tests/vboot_api_kernel6_tests.c +++ b/tests/vboot_api_kernel6_tests.c @@ -43,16 +43,9 @@ static void VbUnlockDeviceTest(void) "set dev fail"); } -static void VbLockDeviceTest(void) -{ - ResetMocks(); - TEST_EQ(VbLockDevice(), 0, "lock success"); -} - int main(void) { VbUnlockDeviceTest(); - VbLockDeviceTest(); return gTestSuccess ? 0 : 255; } |