All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumit Garg <sumit.garg@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Wang Cheng <wanngchenng@gmail.com>,
	jens.wiklander@linaro.org, corbet@lwn.net,
	op-tee@lists.trustedfirmware.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: staging/tee.rst: fix two typos found while reading
Date: Mon, 17 Jan 2022 12:03:04 +0530	[thread overview]
Message-ID: <CAFA6WYM=ie84YO7bBzeXU579LRpxfJ4VMBSkVJy2Fdxd4RpnwQ@mail.gmail.com> (raw)
In-Reply-To: <a6b32e17-9aba-4a03-12db-0d707e0f8d26@infradead.org>

On Sat, 15 Jan 2022 at 21:00, Randy Dunlap <rdunlap@infradead.org> wrote:
>
>
>
> On 1/15/22 04:52, Wang Cheng wrote:
> > Signed-off-by: Wang Cheng <wanngchenng@gmail.com>
>
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
>
> Thanks.
>

Reviewed-by: Sumit Garg <sumit.garg@linaro.org>

-Sumit

> > ---
> >  Documentation/staging/tee.rst | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/staging/tee.rst b/Documentation/staging/tee.rst
> > index 3c63d8dcd61e..498343c7ab08 100644
> > --- a/Documentation/staging/tee.rst
> > +++ b/Documentation/staging/tee.rst
> > @@ -255,7 +255,7 @@ The following picture shows a high level overview of AMD-TEE::
> >   +--------------------------+      +---------+--------------------+
> >
> >  At the lowest level (in x86), the AMD Secure Processor (ASP) driver uses the
> > -CPU to PSP mailbox regsister to submit commands to the PSP. The format of the
> > +CPU to PSP mailbox register to submit commands to the PSP. The format of the
> >  command buffer is opaque to the ASP driver. It's role is to submit commands to
> >  the secure processor and return results to AMD-TEE driver. The interface
> >  between AMD-TEE driver and AMD Secure Processor driver can be found in [6].
> > @@ -290,7 +290,7 @@ cancel_req driver callback is not supported by AMD-TEE.
> >
> >  The GlobalPlatform TEE Client API [5] can be used by the user space (client) to
> >  talk to AMD's TEE. AMD's TEE provides a secure environment for loading, opening
> > -a session, invoking commands and clossing session with TA.
> > +a session, invoking commands and closing session with TA.
> >
> >  References
> >  ==========
>
> --
> ~Randy

  reply	other threads:[~2022-01-17  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15 12:52 [PATCH] docs: staging/tee.rst: fix two typos found while reading Wang Cheng
2022-01-15 15:30 ` Randy Dunlap
2022-01-17  6:33   ` Sumit Garg [this message]
2022-01-17 21:55 ` Jonathan Corbet

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='CAFA6WYM=ie84YO7bBzeXU579LRpxfJ4VMBSkVJy2Fdxd4RpnwQ@mail.gmail.com' \
    --to=sumit.garg@linaro.org \
    --cc=corbet@lwn.net \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=rdunlap@infradead.org \
    --cc=wanngchenng@gmail.com \
    /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.