From: Vegard Nossum <vegard.nossum@oracle.com>
To: Sumit Garg <sumit.garg@linaro.org>,
corbet@lwn.net, jens.wiklander@linaro.org
Cc: Rijo-john.Thomas@amd.com, balint.dobszay@arm.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
op-tee@lists.trustedfirmware.org
Subject: Re: [PATCH] Documentation: Destage TEE subsystem documentation
Date: Tue, 31 Oct 2023 11:16:21 +0100 [thread overview]
Message-ID: <0de17ec7-b692-4d1e-b059-c5f3f619e94a@oracle.com> (raw)
In-Reply-To: <20231031100742.98859-1-sumit.garg@linaro.org>
On 31/10/2023 11:07, Sumit Garg wrote:
> Add a separate documentation directory for TEE subsystem since it is a
> standalone subsystem which already offers devices consumed by multiple
> different subsystem drivers.
>
> Split overall TEE subsystem documentation modularly where the first
> module covers the overview of TEE subsystem itself along with generic
> features. Then the further modules are dedicated to different TEE
> implementations like:
> - OP-TEE
> - AMD-TEE
> - and so on for future TEE implementation support.
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
> Documentation/staging/index.rst | 1 -
> Documentation/staging/tee.rst | 364 -------------------------------
> Documentation/subsystem-apis.rst | 1 +
> Documentation/tee/amd-tee.rst | 90 ++++++++
> Documentation/tee/index.rst | 19 ++
> Documentation/tee/op-tee.rst | 166 ++++++++++++++
> Documentation/tee/tee.rst | 122 +++++++++++
> MAINTAINERS | 2 +-
> 8 files changed, 399 insertions(+), 366 deletions(-)
> delete mode 100644 Documentation/staging/tee.rst
> create mode 100644 Documentation/tee/amd-tee.rst
> create mode 100644 Documentation/tee/index.rst
> create mode 100644 Documentation/tee/op-tee.rst
> create mode 100644 Documentation/tee/tee.rst
A comment from the peanut gallery:
The old tee.rst starts out describing the userspace API (include/uapi/,
/dev/tee, etc.). Maybe this part should go into
Documentation/userspace-api/.
The rest of the document describes the internal kernel API (how to write
a TEE driver). And maybe this part should go into Documentation/driver-api/.
At least I think that kind of split is what the documentation is going
for in the long term, so if you're moving these files around anyway it
might make sense to do it right away.
Vegard
next prev parent reply other threads:[~2023-10-31 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 10:07 Sumit Garg
2023-10-31 10:16 ` Vegard Nossum [this message]
2023-10-31 10:36 ` Sumit Garg
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=0de17ec7-b692-4d1e-b059-c5f3f619e94a@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=Rijo-john.Thomas@amd.com \
--cc=balint.dobszay@arm.com \
--cc=corbet@lwn.net \
--cc=jens.wiklander@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@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
all inboxes | Powered by JetHome®