From: Zack Weinberg <zackw@panix.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>,
GNU C Library <libc-alpha@sourceware.org>,
LKML <linux-kernel@vger.kernel.org>,
gcc-patches@gcc.gnu.org,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
bpf <bpf@vger.kernel.org>
Subject: Re: [RFC] bpf.2: Use standard types and attributes
Date: Sun, 25 Apr 2021 15:12:05 -0400 [thread overview]
Message-ID: <CAKCAbMhaaxiR6HpFZB=bjWyCdNNaA-5ehiujW0TrNuKvQPV=2g@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQJU=r0qE-4ZHsvX4YndbFgDGvzAgNgVo7kPMGF4jCrVeg@mail.gmail.com>
On Sun, Apr 25, 2021 at 12:52 PM Alexei Starovoitov via Libc-alpha
<libc-alpha@sourceware.org> wrote:
> On Sat, Apr 24, 2021 at 10:56 AM Alejandro Colomar (man-pages)
> <alx.manpages@gmail.com> wrote:
> >
> > Hello Alexei,
> >
> > On 4/24/21 1:20 AM, Alexei Starovoitov wrote:
> > > Nack.
> > > The man page should describe the kernel api the way it is in .h file.
> >
> > Why?
>
> Because man page must describe the linux uapi headers the way they
> are installed in the system and not invent alternative implementations.
> The users will include those .h with __u32 and will see them in their code.
> Man page saying something else is a dangerous lie.
Why do you consider it _dangerous_ for the manpages to replace __u32
with uint32_t, when we know by construction that the two types will
always be the same? Alejandro's preference for the types standardized
by ISO C seems perfectly reasonable to me for documentation; people
reading the documentation can be expected to already know what they
mean, unlike the Linux-specifc __[iu]NN types. Also, all else being
equal, documentation should avoid use of symbols in the ISO C reserved
namespace.
If anything I would argue that it is the uapi headers that should be
changed, to use the <stdint.h> types.
zw
next prev parent reply other threads:[~2021-04-25 19:28 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 23:06 [RFC] bpf.2: Use standard types and attributes Alejandro Colomar
2021-04-23 23:20 ` Alexei Starovoitov
2021-04-24 17:56 ` Alejandro Colomar (man-pages)
2021-04-25 16:52 ` Alexei Starovoitov
2021-04-25 19:12 ` Zack Weinberg [this message]
2021-04-24 20:43 ` David Laight
2021-04-25 19:16 ` Zack Weinberg
2021-04-25 21:09 ` David Laight
2021-04-26 17:19 ` Joseph Myers
2021-04-26 17:46 ` Alejandro Colomar (man-pages)
2021-05-04 11:05 ` [RFC v2] " Alejandro Colomar
2021-05-04 14:12 ` Alexei Starovoitov
2021-05-04 14:24 ` Greg KH
2021-05-04 15:53 ` Alejandro Colomar (man-pages)
2021-05-04 16:06 ` Greg KH
2021-05-04 18:37 ` Zack Weinberg
2021-05-04 18:54 ` Alejandro Colomar (man-pages)
2021-05-04 19:45 ` Florian Weimer
2021-05-04 19:59 ` Alejandro Colomar (man-pages)
2021-05-05 8:23 ` David Laight
2021-05-05 22:22 ` Joseph Myers
2021-05-04 20:06 ` Daniel Borkmann
2021-05-04 20:16 ` Alejandro Colomar (man-pages)
2021-05-04 20:33 ` Zack Weinberg
2021-05-04 21:23 ` Alexei Starovoitov
2021-05-15 19:01 ` [PATCH v3] " Alejandro Colomar
2021-05-16 9:16 ` Alejandro Colomar (man-pages)
2021-05-17 18:56 ` Daniel Borkmann
2021-05-21 11:12 ` Alejandro Colomar
2021-05-04 16:08 ` [RFC v2] " Daniel Borkmann
2022-08-24 18:55 ` [LTP] [PATCH v3] Many pages: Document fixed-width types with ISO C naming Alejandro Colomar
2022-08-24 18:55 ` Alejandro Colomar
2022-08-24 22:40 ` Alexei Starovoitov
2022-08-24 22:40 ` [LTP] " Alexei Starovoitov
2022-08-24 23:36 ` Alejandro Colomar
2022-08-24 23:36 ` [LTP] " Alejandro Colomar
2022-08-25 0:52 ` Linus Torvalds
2022-08-25 0:52 ` Linus Torvalds
2022-08-25 7:20 ` [LTP] " Alejandro Colomar
2022-08-25 7:20 ` Alejandro Colomar
2022-08-25 7:28 ` Xi Ruoyao
2022-08-25 7:28 ` [LTP] " Xi Ruoyao via ltp
2022-08-25 7:48 ` Alejandro Colomar
2022-08-25 7:48 ` Alejandro Colomar
2022-08-25 8:09 ` Xi Ruoyao
2022-08-25 8:09 ` [LTP] " Xi Ruoyao via ltp
2022-08-25 7:42 ` Linus Torvalds
2022-08-25 7:42 ` Linus Torvalds
2022-08-25 7:59 ` [LTP] " Alejandro Colomar
2022-08-25 7:59 ` Alejandro Colomar
2022-08-25 5:57 ` [LTP] " Greg Kroah-Hartman
2022-08-25 5:57 ` Greg Kroah-Hartman
2022-08-25 6:41 ` Florian Weimer
2022-08-25 6:41 ` [LTP] " Florian Weimer
2022-08-25 7:27 ` Linus Torvalds
2022-08-25 7:27 ` [LTP] " Linus Torvalds
2022-08-25 14:38 ` Joseph Myers
2022-08-25 14:38 ` [LTP] " Joseph Myers
2022-08-25 15:01 ` David Laight
2022-08-25 15:01 ` David Laight
2022-08-25 15:37 ` Joseph Myers
2022-08-25 15:37 ` [LTP] " Joseph Myers
2022-08-25 16:43 ` Linus Torvalds
2022-08-25 16:43 ` Linus Torvalds
2022-08-25 7:44 ` [LTP] " Alejandro Colomar
2022-08-25 7:44 ` Alejandro Colomar
2022-08-25 8:04 ` [LTP] " Alejandro Colomar
2022-08-25 8:04 ` 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='CAKCAbMhaaxiR6HpFZB=bjWyCdNNaA-5ehiujW0TrNuKvQPV=2g@mail.gmail.com' \
--to=zackw@panix.com \
--cc=alexei.starovoitov@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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.