summaryrefslogtreecommitdiff
path: root/futility/cmd_sign.c
diff options
context:
space:
mode:
authorRandall Spangler <rspangler@chromium.org>2016-10-13 16:16:41 -0700
committerchrome-bot <chrome-bot@chromium.org>2016-10-23 13:33:38 -0700
commit664096bd1a7247b751bf4e564738d53a1e2795c2 (patch)
tree86d7135e77b942c7121885489c72c067005288a0 /futility/cmd_sign.c
parent08d56aa7a7df69e80aa0a1fd6e847aa1adde5f9c (diff)
downloadvboot-664096bd1a7247b751bf4e564738d53a1e2795c2.tar.gz
vboot: use standard memcmp, memcpy, memset
Originally, we didn't trust the firmware to provide these functions from a standard library. Now, with coreboot, we do. BUG=chromium:611535 BRANCH=none TEST=make runtests; emerge-kevin coreboot depthcharge Change-Id: I4e624c40085f2b665275a38624340b2f6aabcf11 Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/399120 Reviewed-by: Daisuke Nojiri <dnojiri@chromium.org>
Diffstat (limited to 'futility/cmd_sign.c')
-rw-r--r--futility/cmd_sign.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/futility/cmd_sign.c b/futility/cmd_sign.c
index cd46c8ba..661eb3da 100644
--- a/futility/cmd_sign.c
+++ b/futility/cmd_sign.c
@@ -241,7 +241,7 @@ int ft_sign_kern_preamble(const char *name, uint8_t *buf, uint32_t len,
/* If we're modifying an existing file, it's mmap'ed so that
* all our modifications to the buffer will get flushed to
* disk when we close it. */
- Memcpy(kpart_data, vblock_data, vblock_size);
+ memcpy(kpart_data, vblock_data, vblock_size);
}
free(vblock_data);