public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] persistent-keyring.7: wfix
@ 2023-02-07 21:40 Jakub Wilk
  2023-02-07 23:42 ` Alejandro Colomar
  0 siblings, 1 reply; 2+ messages in thread
From: Jakub Wilk @ 2023-02-07 21:40 UTC (permalink / raw)
  To: Michael Kerrisk, Alejandro Colomar
  Cc: linux-man, keyrings, David Howells, Helge Kreutzmann

Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
---

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
-- 
2.39.1


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] persistent-keyring.7: wfix
  2023-02-07 21:40 [PATCH] persistent-keyring.7: wfix Jakub Wilk
@ 2023-02-07 23:42 ` Alejandro Colomar
  0 siblings, 0 replies; 2+ messages in thread
From: Alejandro Colomar @ 2023-02-07 23:42 UTC (permalink / raw)
  To: Jakub Wilk, Michael Kerrisk
  Cc: linux-man, keyrings, David Howells, Helge Kreutzmann


[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-02-07 23:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-02-07 21:40 [PATCH] persistent-keyring.7: wfix Jakub Wilk
2023-02-07 23:42 ` Alejandro Colomar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox