From: Randy Dunlap <rdunlap@infradead.org>
To: jeffxu@chromium.org, akpm@linux-foundation.org,
keescook@chromium.org, jannh@google.com, sroettger@google.com,
willy@infradead.org, gregkh@linuxfoundation.org,
torvalds@linux-foundation.org, usama.anjum@collabora.com
Cc: jeffxu@google.com, jorgelo@chromium.org, groeck@chromium.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, pedro.falcato@gmail.com,
dave.hansen@intel.com, linux-hardening@vger.kernel.org,
deraadt@openbsd.org
Subject: Re: [PATCH v6 4/4] mseal:add documentation
Date: Fri, 12 Jan 2024 17:10:10 -0800 [thread overview]
Message-ID: <8cb16dfe-993e-4c41-b1fe-63bc7ac97609@infradead.org> (raw)
In-Reply-To: <20240111234142.2944934-5-jeffxu@chromium.org>
Hi Jeff,
On 1/11/24 15:41, jeffxu@chromium.org wrote:
> From: Jeff Xu <jeffxu@chromium.org>
>
> Add documentation for mseal().
>
> Signed-off-by: Jeff Xu <jeffxu@chromium.org>
> ---
> Documentation/userspace-api/mseal.rst | 181 ++++++++++++++++++++++++++
> 1 file changed, 181 insertions(+)
> create mode 100644 Documentation/userspace-api/mseal.rst
>
To prevent the following documentation build warning:
linux-next-20240112/Documentation/userspace-api/mseal.rst: WARNING: document isn't included in any toctree
please add the following to your patch 4/4:
diff -- a/Documentation/userspace-api/index.rst b/Documentation/userspace-api/index.rst
--- a/Documentation/userspace-api/index.rst
+++ b/Documentation/userspace-api/index.rst
@@ -23,6 +23,7 @@ place where this information is gathered
ebpf/index
ELF
ioctl/index
+ mseal
iommu
iommufd
media/index
--
#Randy
next prev parent reply other threads:[~2024-01-13 1:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 23:41 [PATCH v6 0/4] Introduce mseal() jeffxu
2024-01-11 23:41 ` [PATCH v6 1/4] mseal: Wire up mseal syscall jeffxu
2024-01-11 23:41 ` [PATCH v6 2/4] mseal: add " jeffxu
2024-01-13 19:48 ` Kees Cook
2024-01-14 3:48 ` Jeff Xu
2024-01-11 23:41 ` [PATCH v6 3/4] selftest mm/mseal memory sealing jeffxu
2024-01-11 23:41 ` [PATCH v6 4/4] mseal:add documentation jeffxu
2024-01-13 1:10 ` Randy Dunlap [this message]
2024-01-13 4:51 ` Jeff Xu
2024-01-13 2:19 ` [PATCH v6 0/4] Introduce mseal() Randy Dunlap
2024-01-13 4:53 ` Jeff Xu
2024-01-13 5:57 ` Randy Dunlap
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=8cb16dfe-993e-4c41-b1fe-63bc7ac97609@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=deraadt@openbsd.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=jeffxu@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pedro.falcato@gmail.com \
--cc=sroettger@google.com \
--cc=torvalds@linux-foundation.org \
--cc=usama.anjum@collabora.com \
--cc=willy@infradead.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).