From: Alejandro Colomar <alx.manpages@gmail.com>
To: Rumen Telbizov <rumen.telbizov@menlosecurity.com>
Cc: linux-man@vger.kernel.org, quentin@isovalent.com
Subject: Re: Update bpf-helpers(7) man page
Date: Tue, 19 Jul 2022 16:42:16 +0200 [thread overview]
Message-ID: <a62a00a3-e673-8874-73b2-57e8d9c362c4@gmail.com> (raw)
In-Reply-To: <CA+FoirBpBrvp7Qme_sqViKf-90tG+s+tUZNy9fmZXEF5u4sx8w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1582 bytes --]
Hi Rumen,
On 7/18/22 18:37, Rumen Telbizov wrote:
> Hi Michael, everyone,
>
> I was directed to you by Quentin Monnet with regards to a missing
> function in the bpf-helpers(7) Linux man page. I found out that the
> man page doesn't have anything regarding bpf_redirect_neigh(). Quentin
> mentioned that he has a script which generates the man page from the
> comments in the source code, but then I am not sure how and when the
> man page is being generated so that it gets out of date. This function
> definitely has comments/documentation in the code and it works
> properly but is missing in the man page.
>
> Is this something you can help with?
Yes, the page is generated:
alx@asus5775:~/src/linux/man-pages/man-pages$ cat MAINTAINER_NOTES
Externally generated pages
==========================
A few pages come from external sources. Fixes to the pages should really
go to the upstream source.
tzfile(5), zdump(8), and zic(8) come from the tz project
(https://www.iana.org/time-zones).
bpf-helpers(7) is autogenerated from the kernel sources using scripts.
See man-pages commit 53666f6c30451cde022f65d35a8d448f5a7132ba for
details.
If Quentin has the script, he could send it to me as a patch to the
man-pages repo, so that it's added to our scripts/ directory. I can
regenerate the page whenever I'm requested to do so, but I've never done
it, so I need the script and a simple explanation to use it.
Thanks,
Alex
>
> Thank you,
> Rumen Telbizov
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-19 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 16:37 Update bpf-helpers(7) man page Rumen Telbizov
2022-07-19 14:42 ` Alejandro Colomar [this message]
2022-07-19 17:21 ` Rumen Telbizov
2022-07-20 9:50 ` Alejandro Colomar
2022-07-20 20:40 ` Quentin Monnet
2022-07-20 21:06 ` Alejandro Colomar
2022-07-20 21:44 ` Quentin Monnet
2022-07-20 21:47 ` Alejandro Colomar
2022-07-20 22:44 ` Rumen Telbizov
2022-07-21 11:27 ` Alejandro Colomar
2022-07-21 18:16 ` Rumen Telbizov
2022-08-24 16:02 ` Jakub Wilk
2022-08-24 16:48 ` Quentin Monnet
2022-08-24 22:07 ` Quentin Monnet
2022-08-24 22:51 ` 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=a62a00a3-e673-8874-73b2-57e8d9c362c4@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=rumen.telbizov@menlosecurity.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