public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>, Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, keyrings@vger.kernel.org,
	David Howells <dhowells@redhat.com>,
	Helge Kreutzmann <debian@helgefjell.de>
Subject: Re: [PATCH] persistent-keyring.7: wfix
Date: Wed, 8 Feb 2023 00:42:08 +0100	[thread overview]
Message-ID: <de6514d4-e8d2-0f87-8610-a5c3393caf50@gmail.com> (raw)
In-Reply-To: <20230207214004.6013-1-jwilk@jwilk.net>


[-- Attachment #1.1: Type: text/plain, Size: 1548 bytes --]

Hi Jakub!

On 2/7/23 22:40, Jakub Wilk wrote:
> Reported-by: Helge Kreutzmann <debian@helgefjell.de>
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>

Thanks for the patch!  Applied.

Cheers,

Alex

> ---
> 
> I have no idea what I'm doing, but the original text was confusing,
> and changing "key" to "keyring" seems consistent with other
> documentation (keyrings.7, keyctl_get_persistent.3).
> 
>  man7/persistent-keyring.7 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/man7/persistent-keyring.7 b/man7/persistent-keyring.7
> index 2a7fe49c2..bf3e33ef5 100644
> --- a/man7/persistent-keyring.7
> +++ b/man7/persistent-keyring.7
> @@ -33,7 +33,7 @@ operation, it will be automatically created.
>  Each time the
>  .BR keyctl_get_persistent (3)
>  operation is performed,
> -the persistent key's expiration timer is reset to the value in:
> +the persistent keyring's expiration timer is reset to the value in:
>  .PP
>  .in +4n
>  .EX
> @@ -44,7 +44,7 @@ the persistent key's expiration timer is reset to the value in:
>  Should the timeout be reached,
>  the persistent keyring will be removed and
>  everything it pins can then be garbage collected.
> -The key will then be re-created on a subsequent call to
> +The keyring will then be re-created on a subsequent call to
>  .BR keyctl_get_persistent (3).
>  .PP
>  The persistent keyring is not directly searched by

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-02-07 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 21:40 [PATCH] persistent-keyring.7: wfix Jakub Wilk
2023-02-07 23:42 ` Alejandro Colomar [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=de6514d4-e8d2-0f87-8610-a5c3393caf50@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=dhowells@redhat.com \
    --cc=jwilk@jwilk.net \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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