linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: update self-protection __ro_after_init status
Date: Fri, 10 Dec 2021 14:02:18 -0700	[thread overview]
Message-ID: <87r1akqilh.fsf@meer.lwn.net> (raw)
In-Reply-To: <20211208164051.8783-1-skhan@linuxfoundation.org>

Shuah Khan <skhan@linuxfoundation.org> writes:

> __ro_after_init is no longer new and under development. Update the
> document to reflect the correct status.
>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> ---
>  Documentation/security/self-protection.rst | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/security/self-protection.rst b/Documentation/security/self-protection.rst
> index f584fb74b4ff..910668e665cb 100644
> --- a/Documentation/security/self-protection.rst
> +++ b/Documentation/security/self-protection.rst
> @@ -81,8 +81,7 @@ of the kernel, gaining the protection of the kernel's strict memory
>  permissions as described above.
>  
>  For variables that are initialized once at ``__init`` time, these can
> -be marked with the (new and under development) ``__ro_after_init``
> -attribute.
> +be marked with the ``__ro_after_init`` attribute.
>  
Applied, thanks.

jon

      reply	other threads:[~2021-12-10 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 16:40 [PATCH] docs: update self-protection __ro_after_init status Shuah Khan
2021-12-10 21:02 ` 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=87r1akqilh.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.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).