All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
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, Jeff Xu <jeffxu@chromium.org>
Subject: Re: [RFC PATCH v4 4/4] mseal:add documentation
Date: Tue, 16 Jan 2024 13:13:10 -0700	[thread overview]
Message-ID: <87y1cp9gvd.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240104185138.169307-5-jeffxu@chromium.org>

jeffxu@chromium.org writes:

> 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

You need to add this file to index.rst or it won't be part of the docs
build.  Sphinx should have warned you about that when you did your test
build.

Thanks,

jon

  parent reply	other threads:[~2024-01-16 20:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 18:51 [RFC PATCH v4 0/4] Introduce mseal() jeffxu
2024-01-04 18:51 ` [RFC PATCH v4 1/4] mseal: Wire up mseal syscall jeffxu
2024-01-05  7:44   ` Greg KH
2024-01-05 19:37     ` Jeff Xu
2024-01-04 18:51 ` [RFC PATCH v4 2/4] mseal: add " jeffxu
2024-01-07 18:41   ` Linus Torvalds
2024-01-08 16:00     ` Jeff Xu
2024-01-04 18:51 ` [RFC PATCH v4 3/4] selftest mm/mseal memory sealing jeffxu
2024-01-09  7:17   ` Muhammad Usama Anjum
2024-01-11  3:04     ` Jeff Xu
2024-01-04 18:51 ` [RFC PATCH v4 4/4] mseal:add documentation jeffxu
2024-01-04 23:47   ` Randy Dunlap
2024-01-05 19:37     ` Jeff Xu
2024-01-16 20:13   ` Jonathan Corbet [this message]
2024-01-16 20:48     ` Jeff Xu
2024-01-16 22:19     ` 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=87y1cp9gvd.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.