From 897a95f46c1aa15db24fd8cebff5b136cadb40a1 Mon Sep 17 00:00:00 2001 From: Dave Rodgman Date: Wed, 30 Jun 2021 18:50:57 +0100 Subject: [PATCH] Move subsection Signed-off-by: Dave Rodgman --- docs/3.0-migration-guide.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/3.0-migration-guide.md b/docs/3.0-migration-guide.md index 2e08640d1..09e5bd870 100644 --- a/docs/3.0-migration-guide.md +++ b/docs/3.0-migration-guide.md @@ -254,12 +254,6 @@ This makes no difference to a vast majority of applications. If your code takes Alternative implementations of the SHA256 and SHA512 modules must adjust their functions' prototype accordingly. - -## High-level crypto - -Please also refer to the section [Low-level crypto](#low-level-crypto) for -changes that could sit in either category. - ### Deprecated error codes for hardware failures were removed - The macros `MBEDTLS_ERR_xxx_FEATURE_UNSUPPORTED` from various crypto modules @@ -268,6 +262,12 @@ changes that could sit in either category. - The macros `MBEDTLS_ERR_xxx_HW_ACCEL_FAILED` from various crypto modules were removed; `MBEDTLS_ERR_PLATFORM_HW_ACCEL_FAILED` is now used instead. + +## High-level crypto + +Please also refer to the section [Low-level crypto](#low-level-crypto) for +changes that could sit in either category. + ### Calling `mbedtls_cipher_finish()` is mandatory for all multi-part operations This only affects people who use the cipher module to perform AEAD operations