From: Ulrich Drepper <drepper@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davidel@xmailserver.org, mtk.manpages@gmail.com,
torvalds@linux-foundation.org
Subject: Re: [PATCH 02/18] flag parameters: socket and socketpair
Date: Mon, 05 May 2008 20:02:55 -0700 [thread overview]
Message-ID: <481FCA5F.1000101@redhat.com> (raw)
In-Reply-To: <20080505194221.4349418b.akpm@linux-foundation.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Morton wrote:
> oh. More overhead.
One alternative: I can simply do away with the remapping and just
allocate the bits for the new constants (EFD_CLOEXEC) to match those of
the O_* constants. This means we can still reuse the low bits which
aren't available in the O_* constants. It means, though, that the
constants are architecture specific since O_CLOEXEC, for instance, has
different values for different architectures.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFIH8pf2ijCOnn/RHQRAnlPAKCPxPVuaW+nXpCaxNsPmrAunBqt6gCfetlU
41ZicojDFl0TmVX34p8Z1CA=
=q+B/
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-05-06 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 3:42 [PATCH 02/18] flag parameters: socket and socketpair Ulrich Drepper
2008-05-05 4:24 ` YOSHIFUJI Hideaki / 吉藤英明
2008-05-05 5:00 ` Ulrich Drepper
2008-05-05 8:11 ` David Miller
2008-05-06 1:58 ` Andrew Morton
2008-05-06 2:13 ` Davide Libenzi
2008-05-06 2:17 ` Andrew Morton
2008-05-06 2:30 ` Davide Libenzi
2008-05-06 11:43 ` Alan Cox
2008-05-06 2:33 ` Ulrich Drepper
2008-05-06 2:42 ` Andrew Morton
2008-05-06 2:58 ` Ulrich Drepper
2008-05-06 3:05 ` Andrew Morton
2008-05-06 3:10 ` Ulrich Drepper
2008-05-06 3:02 ` Ulrich Drepper [this message]
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=481FCA5F.1000101@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.