From: Jonathan Corbet <corbet@lwn.net>
To: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Cc: dhowells@redhat.com, jarkko.sakkinen@linux.intel.com,
keyrings@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] Documentation: security: core.rst: fix warnings
Date: Fri, 22 Nov 2019 10:02:01 -0700 [thread overview]
Message-ID: <20191122100201.30b1e71f@lwn.net> (raw)
In-Reply-To: <20191122041806.68650-1-dwlsalmeida@gmail.com>
On Fri, 22 Nov 2019 01:18:06 -0300
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com> wrote:
> From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
>
> Fix warnings due to missing markup, no change in content otherwise.
>
> Signed-off-by: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
> ---
> Documentation/security/keys/core.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/security/keys/core.rst b/Documentation/security/keys/core.rst
> index d6d8b0b756b6..d9b0b859018b 100644
> --- a/Documentation/security/keys/core.rst
> +++ b/Documentation/security/keys/core.rst
> @@ -1102,7 +1102,7 @@ payload contents" for more information.
> See also Documentation/security/keys/request-key.rst.
>
>
> - * To search for a key in a specific domain, call:
> + * To search for a key in a specific domain, call::
>
> struct key *request_key_tag(const struct key_type *type,
> const char *description,
Applied, thanks.
jon
next prev parent reply other threads:[~2019-11-22 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 4:18 [PATCH] Documentation: security: core.rst: fix warnings Daniel W. S. Almeida
2019-11-22 17:02 ` Jonathan Corbet [this message]
2019-11-29 20:57 ` Jarkko Sakkinen
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=20191122100201.30b1e71f@lwn.net \
--to=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dwlsalmeida@gmail.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.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