Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Petr Vorel <pvorel@suse.cz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/1] man/man2/request_key.2: Add missing GNU size forward-declarations
Date: Mon, 14 Sep 2026 13:44:04 +0200	[thread overview]
Message-ID: <aqfd1_Xa_TbzE1ML@devuan> (raw)
In-Reply-To: <20260914111511.1610878-1-pvorel@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

Hi Petr,

> Date: 2026-09-14 13:15:11+0200
> From: Petr Vorel <pvorel@suse.cz>
>
> request_key was left from GNU forward-declarations of parameters for
> sizes of array parameters.
> 
> Fixes: d2c2db883 ("man/: SYNOPSIS: Use GNU forward-declarations of parameters for sizes of array parameters")
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Hi Alejandro,
> 
> although I don't like N3207 GNU forward-declarations of parameters for
> sizes of array parameters syntax (I'd prefer to have the signatures
> which are in the headers) and I don't think it's practical (before one
> could copy paste the signature from man page), I understand it's a
> wanted feature. Therefore I fixed missing size parameter in request_key.
> 
> I suppose more functions were left in d2c2db883.
> 
> Kind regards,
> Petr
> 
>  man/man2/request_key.2 | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/man/man2/request_key.2 b/man/man2/request_key.2
> index 3bb52f31b..d16642d9f 100644
> --- a/man/man2/request_key.2
> +++ b/man/man2/request_key.2
> @@ -14,7 +14,8 @@ Linux Key Management Utilities
>  .nf
>  .B #include <keyutils.h>
>  .P
> -.BI "key_serial_t request_key(const char *" type ", const char *" description ,
> +.BR "key_serial_t request_key(" "size_t size;"
> +.BI "                         (const char *" type ", const char *" description ,
>  .BI "                         const char *_Nullable " callout_info ,
>  .BI "                         key_serial_t " dest_keyring );

I don't see the 'size' being a parameter of this function at all.  Am
I missing something?


Have a lovely day!
Alex

>  .fi
> -- 
> 2.55.0
> 

-- 
<https://www.alejandro-colomar.es>

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

  reply	other threads:[~2026-09-14 11:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 11:15 [PATCH 1/1] man/man2/request_key.2: Add missing GNU size forward-declarations Petr Vorel
2026-09-14 11:44 ` Alejandro Colomar [this message]
2026-09-14 12:24   ` Petr Vorel
2026-09-14 13:30     ` Alejandro Colomar
2026-09-14 17:19       ` Mark Harris
2026-09-14 18:12         ` Alejandro Colomar
2026-09-14 18:34           ` Martin Uecker
2026-09-14 21:03             ` Alejandro Colomar
2026-09-15  6:08               ` Martin Uecker
2026-09-15  9:02                 ` Alejandro Colomar
2026-09-15  9:45                   ` Martin Uecker
2026-09-15  9:59                     ` Alejandro Colomar
2026-09-15 10:28                       ` Martin Uecker
2026-09-15 10:56                         ` Alejandro Colomar
2026-09-14 18:37         ` status of C forward declarations (was: [PATCH 1/1] man/man2/request_key.2: Add missing GNU size forward-declarations) G. Branden Robinson
2026-09-14 21:06           ` Alejandro Colomar

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=aqfd1_Xa_TbzE1ML@devuan \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=pvorel@suse.cz \
    /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