[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7zsiwtuwz3ybq6cymwkfbp2fxiliof25ko2zk77cgitfsxxgc6@x5jbr76h3f4s>
Date: Tue, 25 Nov 2025 13:13:01 +0100
From: Alejandro Colomar <alx@...nel.org>
To: dzwdz <not@...dz.net>
Cc: linux-man@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>, ej@...i.de
Subject: Re: [PATCH 0/2] man7/ip.7: Clarify PKTINFO's docs
Hi dzwdz,
On Tue, Nov 25, 2025 at 02:50:19AM +0100, dzwdz wrote:
> On 11/18/25 14:51, Alejandro Colomar wrote:
> > Do you suggest moving each socket option to a manual page under
> > man2const/? I think I agree with that. There's precedent, and it makes
> > the pages more readable.
>
> In general - yes, definitely!
Done. I've split ip(7) into a large amount of small pages this weekend.
Please have a look at them and suggest any improvements you consider
appropriate. ;)
> However, struct in_pktinfo can be passed to sendmsg even if IP_PKTINFO isn't
> set, so I don't think it would make sense to document it in e.g.
> IP_PKTINFO(2const) - it should probably get its own manpage in man2type.
> That option, in turn, only makes sense in the context of that struct, so I
> think it should probably be documented in in_pktinfo(2type).
>
> This would /kinda/ be like how e.g. PA_INT(3const) points to
> printf.h(3head), I guess?
>
> I'd be happy to try writing that manpage if you think this approach makes
> sense :)
Yup, it makes sense. :)
I'll simplify your work by doing some initial changes. Please wait
a couple of days before starting, so I can finish doing that.
Have a lovely day!
Alex
>
> Thanks,
> dzwdz
--
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists