From: Oliver Falk <oliver@linux-kernel.at>
To: libc-ports@sourceware.org
Subject: Re: alpha fcntl bits missing defines
Date: Wed, 23 Feb 2011 12:48:00 -0000 [thread overview]
Message-ID: <4D6501F9.9010202@linux-kernel.at> (raw)
In-Reply-To: <4D64F4E6.8000702@linux-kernel.at>
Hi!
On 02/23/2011 12:52 PM, Oliver Falk wrote:
> Just noticed, that [ports]/sysdeps/unix/sysv/linux/alpha/bits/fcntl.h is
> missing the following 2 defines:
>
> --- fcntl.h.PIPE_SZ 2011-02-23 10:46:09.000000000 +0100
> +++ fcntl.h 2011-02-23 10:46:11.000000000 +0100
> @@ -97,6 +97,8 @@
> # define F_SETLEASE 1024 /* Set a lease. */
> # define F_GETLEASE 1025 /* Enquire what lease is active. */
> # define F_NOTIFY 1026 /* Request notfications on a directory. */
> +# define F_SETPIPE_SZ 1031 /* Set pipe page size array. */
> +# define F_GETPIPE_SZ 1032 /* Set pipe page size array. */
> #endif
> #ifdef __USE_XOPEN2K8
> # define F_DUPFD_CLOEXEC 1030 /* Duplicate file descriptor with
>
> Would be great if one could add it.
And another small patch for statfs.h:
--- statfs.h.f_flags 2011-02-23 11:23:06.000000000 +0100
+++ statfs.h 2011-02-23 11:26:21.000000000 +0100
@@ -42,6 +42,7 @@
__fsid_t f_fsid;
int f_namelen;
int f_frsize;
+ int f_flags;
int f_spare[5];
};
@@ -58,6 +59,7 @@
__fsid_t f_fsid;
int f_namelen;
int f_frsize;
+ int f_flags;
int f_spare[5];
};
#endif
-of
next prev parent reply other threads:[~2011-02-23 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 11:52 Oliver Falk
2011-02-23 12:48 ` Oliver Falk [this message]
2011-02-23 13:36 ` Andreas Schwab
2011-02-23 14:14 ` Oliver Falk
2011-02-23 16:57 ` Matt Turner
2011-02-23 18:04 ` Oliver Falk
2011-02-23 23:12 ` __atfct_seterrno problem while linking Oliver Falk
2011-02-23 23:26 ` Matt Turner
2011-02-24 10:08 ` Oliver Falk
2011-02-24 10:20 ` Oliver Falk
2011-02-24 15:24 ` Oliver Falk
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=4D6501F9.9010202@linux-kernel.at \
--to=oliver@linux-kernel.at \
--cc=libc-ports@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).