linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: jens.wiklander@linaro.org, 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 v3] Documentation: Destage TEE subsystem documentation
Date: Fri, 08 Dec 2023 15:52:11 -0700	[thread overview]
Message-ID: <87fs0c489w.fsf@meer.lwn.net> (raw)
In-Reply-To: <20231128072352.866859-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.
>
> Acked-by: Rijo Thomas <Rijo-john.Thomas@amd.com>
> Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> ---
>
> Changes in v3:
> - Rebased to docs-next
> - Fixed dangling references to Documentation/staging/tee.rst.
> - Applied tags.

Applied, thanks.

jon

      reply	other threads:[~2023-12-08 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28  7:23 [PATCH v3] Documentation: Destage TEE subsystem documentation Sumit Garg
2023-12-08 22:52 ` Jonathan Corbet [this message]

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=87fs0c489w.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).