public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Igor Opaniuk <igor.opaniuk@foundries.io>
Cc: u-boot@lists.denx.de, Igor Opaniuk <igor.opaniuk@gmail.com>,
	Jens Wiklander <jens.wiklander@linaro.org>,
	Jorge Ramirez-Ortiz <jorge@foundries.io>,
	Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v1 2/5] tee: sandbox: fix spelling errors
Date: Fri, 1 Mar 2024 08:55:36 +0200	[thread overview]
Message-ID: <ZeF76GLildbEE9bB@hades> (raw)
In-Reply-To: <20240214183444.493629-3-igor.opaniuk@gmail.com>

On Wed, Feb 14, 2024 at 07:34:41PM +0100, Igor Opaniuk wrote:
> Fix spelling errors in comments.
> 
> Signed-off-by: Igor Opaniuk <igor.opaniuk@gmail.com>
> ---
> 
>  drivers/tee/sandbox.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/tee/sandbox.c b/drivers/tee/sandbox.c
> index 86219a9bb1a..ec66401878c 100644
> --- a/drivers/tee/sandbox.c
> +++ b/drivers/tee/sandbox.c
> @@ -14,7 +14,7 @@
>  #include "optee/optee_private.h"
>  
>  /*
> - * The sandbox tee driver tries to emulate a generic Trusted Exectution
> + * The sandbox tee driver tries to emulate a generic Trusted Execution
>   * Environment (TEE) with the Trusted Applications (TA) OPTEE_TA_AVB and
>   * OPTEE_TA_RPC_TEST available.
>   */
> @@ -23,7 +23,7 @@ static const u32 pstorage_max = 16;
>  /**
>   * struct ta_entry - TA entries
>   * @uuid:		UUID of an emulated TA
> - * @open_session	Called when a session is openened to the TA
> + * @open_session	Called when a session is opened to the TA
>   * @invoke_func		Called when a function in the TA is to be invoked
>   *
>   * This struct is used to register TAs in this sandbox emulation of a TEE.
> @@ -140,8 +140,8 @@ static u32 pta_scp03_invoke_func(struct udevice *dev, u32 func, uint num_params,
>  			provisioned = true;
>  
>  		/*
> -		 * Either way, we asume both operations succeeded and that
> -		 * the communication channel has now been stablished
> +		 * Either way, we assume both operations succeeded and that
> +		 * the communication channel has now been established
>  		 */
>  
>  		return TEE_SUCCESS;
> -- 
> 2.34.1
> 
Reviewed-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>


  parent reply	other threads:[~2024-03-01  6:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 18:34 [PATCH v1 0/5] TEE: minor cleanup Igor Opaniuk
2024-02-14 18:34 ` [PATCH v1 1/5] tee: optee: fix description in Kconfig Igor Opaniuk
2024-02-14 21:40   ` Heinrich Schuchardt
2024-03-01  6:53   ` Ilias Apalodimas
2024-02-14 18:34 ` [PATCH v1 2/5] tee: sandbox: fix spelling errors Igor Opaniuk
2024-02-14 21:41   ` Heinrich Schuchardt
2024-03-01  6:55   ` Ilias Apalodimas [this message]
2024-02-14 18:34 ` [PATCH v1 3/5] cmd: optee_rpmb: build cmd for sandbox Igor Opaniuk
2024-02-15  9:52   ` Mattijs Korpershoek
2024-02-14 18:34 ` [PATCH v1 4/5] test: py: add optee_rpmb tests Igor Opaniuk
2024-02-14 18:34 ` [PATCH v1 5/5] tee: remove common.h inclusion Igor Opaniuk
2024-02-29 19:11 ` [PATCH v1 0/5] TEE: minor cleanup Igor Opaniuk
2024-02-29 19:25   ` Peter Robinson
2024-02-29 19:38     ` Tom Rini
2024-03-01  9:40   ` Ilias Apalodimas
2024-03-02 22:02     ` Igor Opaniuk

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=ZeF76GLildbEE9bB@hades \
    --to=ilias.apalodimas@linaro.org \
    --cc=igor.opaniuk@foundries.io \
    --cc=igor.opaniuk@gmail.com \
    --cc=jens.wiklander@linaro.org \
    --cc=jorge@foundries.io \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox