From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Jens Wiklander <jens.wiklander@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
Maxim Uvarov <maxim.uvarov@linaro.org>,
"tee-dev @ lists . linaro . org" <tee-dev@lists.linaro.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
op-tee@lists.trustedfirmware.org
Subject: Re: [PATCH v2] Documentation: tee: Document TEE kernel interface
Date: Thu, 18 Jun 2020 02:15:11 +0300 [thread overview]
Message-ID: <20200617231511.GE62794@linux.intel.com> (raw)
In-Reply-To: <CAFA6WYOpXmdabrpbyJqeknkwv1NeD4+tp95zP+si23SSXDwJdQ@mail.gmail.com>
On Tue, Jun 16, 2020 at 07:20:17PM +0530, Sumit Garg wrote:
> On Tue, 16 Jun 2020 at 01:49, Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> >
> > On Thu, Jun 04, 2020 at 12:29:39PM +0530, Sumit Garg wrote:
> > > Update documentation with TEE bus infrastructure which provides an
> > > interface for kernel client drivers to communicate with corresponding
> > > Trusted Application.
> > >
> > > Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> >
> > Please at least broadly describe the update in the commit message.
> >
>
> How about following additional info to the above commit description?
>
> Brief description of changes:
> - Add a section to describe TEE kernel interface along with a TEE
> client driver example snippet.
> - Add a sub-section for OP-TEE driver to describe OP-TEE specific
> device enumeration.
>
> -Sumit
>
> > /Jarkko
WFM
/Jarkko
next prev parent reply other threads:[~2020-06-17 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 6:59 [PATCH v2] Documentation: tee: Document TEE kernel interface Sumit Garg
2020-06-04 9:05 ` Maxim Uvarov
2020-06-15 20:19 ` Jarkko Sakkinen
2020-06-16 13:50 ` Sumit Garg
2020-06-17 23:15 ` Jarkko Sakkinen [this message]
2020-06-19 19:42 ` 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=20200617231511.GE62794@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jens.wiklander@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.uvarov@linaro.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@linaro.org \
--cc=tee-dev@lists.linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).