aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBin Chen <bin.chen@linaro.org>2017-02-23 16:20:37 +1100
committerBin Chen <bin.chen@linaro.org>2017-02-23 16:28:35 +1100
commit36eeb5ab78e1161275c559c9054c9b9ab2572ce1 (patch)
tree14663b4555c338be5ea73d39a07e01f0167e207d
parent8d7a55d2505874a5d41cbdbb02fe47e2bcd5522d (diff)
downloadsource.android.com-36eeb5ab78e1161275c559c9054c9b9ab2572ce1.tar.gz
dm-verity: alway use dm-verity (mapping) table
I maybe wrong but feel "dm-verity mapping *hash* table" is a little confusing. It should be just mapping table, or simply table, as used in other section of the article. Remove the "hash" for accuracy and consistency. Test: make online-sac-doc Change-Id: I429efbde46d1c6bd50f1be7ac96f496ee97188e4 Signed-off-by: Bin Chen <bin.chen@linaro.org>
-rw-r--r--src/security/verifiedboot/dm-verity.jd2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/security/verifiedboot/dm-verity.jd b/src/security/verifiedboot/dm-verity.jd
index d14f99b3..f989017b 100644
--- a/src/security/verifiedboot/dm-verity.jd
+++ b/src/security/verifiedboot/dm-verity.jd
@@ -122,7 +122,7 @@ you have only a single hash.</li>
</ol>
<p>The result of this is a single hash, which is your root hash. This and your salt
-are used during the construction of your dm-verity mapping hash table.</p>
+are used during the construction of your dm-verity mapping table.</p>
<h3 id="mapping-table">Building the dm-verity mapping table</h3>