From: Andreas Schwab <schwab@suse.de>
To: Jeff Layton <jlayton@redhat.com>
Cc: Roland McGrath <roland@hack.frob.com>,
libc-alpha@sourceware.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH 1/2] fcntl.h: add new definitions for file-private lock cmd values
Date: Wed, 12 Feb 2014 08:50:24 +0100 [thread overview]
Message-ID: <mvmppms22in.fsf@hawking.suse.de> (raw)
In-Reply-To: <20140211185748.378c67f0@corrin.poochiereds.net> (Jeff Layton's message of "Tue, 11 Feb 2014 18:57:48 -0500")
Jeff Layton <jlayton@redhat.com> writes:
> Why does glibc have its own definitions for the fcntl F_* cmd values
> instead of using the ones in the uapi kernel headers? Would it not be
> simpler to just have the fcntl.h include those instead of duplicating
> them?
The uapi headers are useless for user space. They refer to CONFIG_*
macros, and don't have suitable namespace control.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2014-02-12 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 19:03 [RFC][PATCH 0/2] glibc: header file and manual updates for file-private locks Jeff Layton
2014-02-11 19:03 ` [RFC][PATCH 1/2] fcntl.h: add new definitions for file-private lock cmd values Jeff Layton
2014-02-11 21:49 ` Roland McGrath
2014-02-11 23:57 ` Jeff Layton
2014-02-12 7:50 ` Andreas Schwab [this message]
2014-02-12 23:19 ` Roland McGrath
2014-02-11 19:03 ` [RFC][PATCH 2/2] manual: update manual to document file-private locks Jeff Layton
2014-02-16 8:27 ` [RFC][PATCH 0/2] glibc: header file and manual updates for " Mike Frysinger
2014-02-16 12:42 ` Jeff Layton
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=mvmppms22in.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=jlayton@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=roland@hack.frob.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.