From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH][v2] crypto/fsl: Make function names consistent for blob encapsulation/decapsulation.
Date: Tue, 24 Feb 2015 14:43:14 -0800 [thread overview]
Message-ID: <54ECFE82.4090802@freescale.com> (raw)
In-Reply-To: <1424422048-16008-1-git-send-email-gaurav.rana@freescale.com>
On 02/20/2015 12:47 AM, Gaurav Rana wrote:
> This patch does the following:
>
> 1. The function names for encapsulation and decapsulation
> were inconsitent in freescale's implementation and cmd_blob file.
> This patch corrects the issues.
> 2. The function protopye is also modified to change the length parameter
> from u8 to u32 to allow encapsulation and decapsulation of larger images.
> 3. Modified the description of km paramter in the command usage for better
> readability.
>
> Signed-off-by: Gaurav Rana <gaurav.rana@freescale.com>
> Reviewed-by: Ruchika Gupta <ruchika.gupta@freescale.com>
> ---
> Changes in v2:
> Modify blob_help_text[] array.
>
> common/cmd_blob.c | 18 ++++++++++--------
> drivers/crypto/fsl/fsl_blob.c | 4 ++--
> 2 files changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/common/cmd_blob.c b/common/cmd_blob.c
> index 82ecaf0..6178939 100644
> --- a/common/cmd_blob.c
> +++ b/common/cmd_blob.c
> @@ -90,17 +90,19 @@ static char blob_help_text[] =
> "enc src dst len km - Encapsulate and create blob of data\n"
> " $len bytes long at address $src and\n"
> " store the result at address $dst.\n"
> - " $km is the 16 byte key modifier\n"
> - " is also required for generation/use as\n"
> - " key for cryptographic operation. Key\n"
> - " modifier should be 16 byte long.\n"
> + " $km is the address where the key\n"
> + " modifier is stored.\n"
> + " The modifier is required for generation\n"
> + " /use as key for cryptographic operation.\n"
> + " Key modifier should be 16 byte long.\n"
> "blob dec src dst len km - Decapsulate the blob of data at address\n"
> " $src and store result of $len byte at\n"
> " addr $dst.\n"
> - " $km is the 16 byte key modifier\n"
> - " is also required for generation/use as\n"
> - " key for cryptographic operation. Key\n"
> - " modifier should be 16 byte long.\n";
> + " $km is the address where the key\n"
> + " modifier is stored.\n"
> + " The modifier is required for generation\n"
> + " /use as key for cryptographic operation.\n"
> + " Key modifier should be 16 byte long.\n"
You removed the semicolon here. Did you see any compiling error?
York
next prev parent reply other threads:[~2015-02-24 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 8:47 [U-Boot] [PATCH][v2] crypto/fsl: Make function names consistent for blob encapsulation/decapsulation Gaurav Rana
2015-02-24 22:43 ` York Sun [this message]
2015-02-24 23:20 ` York Sun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54ECFE82.4090802@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.