From: Jonathan Corbet <corbet@lwn.net>
To: Sumit Garg <sumit.garg@linaro.org>, jens.wiklander@linaro.org
Cc: vegard.nossum@oracle.com, Rijo-john.Thomas@amd.com,
balint.dobszay@arm.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, op-tee@lists.trustedfirmware.org,
Sumit Garg <sumit.garg@linaro.org>
Subject: Re: [PATCH v2] Documentation: Destage TEE subsystem documentation
Date: Mon, 27 Nov 2023 10:52:04 -0700 [thread overview]
Message-ID: <87h6l7yth7.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231103061715.196294-1-sumit.garg@linaro.org>
Sumit Garg <sumit.garg@linaro.org> writes:
> 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 userspace API has been moved to Documentation/userspace-api/tee.rst.
> - The driver API has been moved to Documentation/driver-api/tee.rst.
> - The first module covers the overview of TEE subsystem.
> - 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>
> ---
>
> Changes in v2:
> - Move userspace API to Documentation/userspace-api/tee.rst.
> - Move driver API to Documentation/driver-api/tee.rst.
>
> Documentation/driver-api/index.rst | 1 +
> Documentation/driver-api/tee.rst | 66 +++++
> 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 | 22 ++
> Documentation/userspace-api/index.rst | 1 +
> Documentation/userspace-api/tee.rst | 39 +++
> MAINTAINERS | 4 +-
> 12 files changed, 408 insertions(+), 366 deletions(-)
> create mode 100644 Documentation/driver-api/tee.rst
> 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
> create mode 100644 Documentation/userspace-api/tee.rst
So I finally got around to applying this...after dealing with the fact
that it doesn't apply to docs-next, I found that it adds a couple of
warnings:
> Warning: Documentation/security/keys/trusted-encrypted.rst references a file that doesn't exist: Documentation/staging/tee.rst
> Warning: drivers/tee/optee/Kconfig references a file that doesn't exist: Documentation/staging/tee.rst
Can I get a version that doesn't leave dangling references like that
around?
Thanks,
jon
next prev parent reply other threads:[~2023-11-27 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 6:17 [PATCH v2] Documentation: Destage TEE subsystem documentation Sumit Garg
2023-11-07 7:50 ` Rijo Thomas
2023-11-20 5:05 ` Sumit Garg
2023-11-20 14:01 ` Jonathan Corbet
2023-11-20 15:34 ` Sumit Garg
2023-11-20 16:21 ` Jens Wiklander
2023-11-27 17:52 ` Jonathan Corbet [this message]
2023-11-28 7:26 ` 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=87h6l7yth7.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Rijo-john.Thomas@amd.com \
--cc=balint.dobszay@arm.com \
--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 \
--cc=vegard.nossum@oracle.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 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).