All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Boeckel <me@benboeckel.net>
To: keyrings@vger.kernel.org
Cc: Ben Boeckel <mathstuf@gmail.com>, dhowells@redhat.com
Subject: [PATCH 1/1] man: the info strings are actually space or tab separated
Date: Sat, 16 May 2020 00:23:34 +0000	[thread overview]
Message-ID: <20200516002334.2025760-2-list.lkml.keyrings@me.benboeckel.net> (raw)
In-Reply-To: <20200516002334.2025760-1-list.lkml.keyrings@me.benboeckel.net>

From: Ben Boeckel <mathstuf@gmail.com>

Signed-off-by: Ben Boeckel <mathstuf@gmail.com>
---
 man/keyctl_pkey_encrypt.3 | 4 ++--
 man/keyctl_pkey_query.3   | 2 +-
 man/keyctl_pkey_sign.3    | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/man/keyctl_pkey_encrypt.3 b/man/keyctl_pkey_encrypt.3
index 44c640e..5a5b71b 100644
--- a/man/keyctl_pkey_encrypt.3
+++ b/man/keyctl_pkey_encrypt.3
@@ -40,8 +40,8 @@ When invoking the function,
 .I key
 indicates the key that will provide the cryptographic material and
 .I info
-points to a comma-separated string of "key[=value]" parameters that indicate
-things like encoding forms and passwords to unlock the key; see
+points to a space- or tab-separated string of "key[=value]" parameters that
+indicate things like encoding forms and passwords to unlock the key; see
 asymmetric-key(7) for more information.
 .PP
 .IR data " and " datalen
diff --git a/man/keyctl_pkey_query.3 b/man/keyctl_pkey_query.3
index dbeb0fd..e70665f 100644
--- a/man/keyctl_pkey_query.3
+++ b/man/keyctl_pkey_query.3
@@ -32,7 +32,7 @@ When invoking the function,
 .I key
 indicates the key to be queried,
 .I info
-points to a comma-separated string of "key[=value]" parameters and
+points to a space- or tab-separated string of "key[=value]" parameters and
 .I result
 points to a buffer in which the result will be placed.
 .PP
diff --git a/man/keyctl_pkey_sign.3 b/man/keyctl_pkey_sign.3
index 2f17e73..4fb6a14 100644
--- a/man/keyctl_pkey_sign.3
+++ b/man/keyctl_pkey_sign.3
@@ -44,8 +44,8 @@ When invoking the function,
 .I key
 indicates the key that will provide the cryptographic material and
 .I info
-points to a comma-separated string of "key[=value]" parameters that indicate
-things like encoding forms and passwords to unlock the key; see
+points to a space- or tab-separated string of "key[=value]" parameters that
+indicate things like encoding forms and passwords to unlock the key; see
 asymmetric-key(7) for more information.
 .PP
 .IR data " and " datalen
-- 
2.25.4

  reply	other threads:[~2020-05-16  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16  0:23 [PATCH 0/1] Fix mention of comma-separated pkey query strings Ben Boeckel
2020-05-16  0:23 ` Ben Boeckel [this message]
2020-05-18 14:06   ` [PATCH 1/1] man: the info strings are actually space or tab separated David Howells

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=20200516002334.2025760-2-list.lkml.keyrings@me.benboeckel.net \
    --to=me@benboeckel.net \
    --cc=dhowells@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=mathstuf@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 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.