From: Florian Weimer <fweimer@redhat.com>
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>
Cc: Eric Blake <eblake@redhat.com>,
glibc list <libc-alpha@sourceware.org>,
linux-man@vger.kernel.org
Subject: Re: f_owner_ex vs. POSIX
Date: Mon, 02 Sep 2019 15:44:53 +0200 [thread overview]
Message-ID: <87mufmvmlm.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <bdc9527b-6595-9f4e-b35d-3796967e044c@gmail.com> (Michael Kerrisk's message of "Sun, 1 Sep 2019 15:23:36 +0200")
* Michael Kerrisk:
> I do not know what the rationale was for the addition of the 'enum',
> and it wouldn't surprise me if there was no public discussion about
> it. The use of an 'enum' strikes me as a slightly odd decision (given
> that the kernel uses 'int') but, related to your point below, there
> is precedent in, for example, the use of an 'enum' for 'idtype_t' in
> waitid() inside glibc, while the kernel type for the argument in
> the underlying system call is 'int'.
There is also the issue of -fshort-enum. Some people probably expect
that they can use that option and still use glibc headers.
I do not have any inside knowledge why things are like they are.
Presumably we can switch the type member to int.
Thanks,
Florian
next prev parent reply other threads:[~2019-09-02 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 15:50 f_owner_ex vs. POSIX Eric Blake
2019-09-01 13:23 ` Michael Kerrisk (man-pages)
2019-09-02 13:44 ` Florian Weimer [this message]
2019-09-03 3:51 ` Rich Felker
2019-09-09 15:15 ` Eric Blake
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=87mufmvmlm.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=eblake@redhat.com \
--cc=libc-alpha@sourceware.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.