From: Ulrich Drepper <drepper@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, davidel@xmailserver.org,
mtk.manpages@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 18/18] flag parameters: check magic constants
Date: Mon, 12 May 2008 21:21:29 -0700 [thread overview]
Message-ID: <48291749.1060400@redhat.com> (raw)
In-Reply-To: <20080512.210225.167924945.davem@davemloft.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Miller wrote:
> You'll need to handle MIPS and PARISC as well, as they have
> similar conflicts.
Is MIPS really a problem? The value is 0x80. 128 protocol types should
be enough. Even if not, there is no reason why the numbers should be
consecutive. It's easy enough to skip over a bit. I.e., after procotol
0x7f the next one would be 0x100.
And PA seems to have gotten O_NONBLOCK wrong. SPARC does it right AFAICS.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFIKRdJ2ijCOnn/RHQRAovKAKDFz2ZJ0E2XYVu5Qn8fME+ieZZopwCgmH4D
ldfvNrhK8LdvjZzNPViILV0=
=Z9Dj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-05-13 4:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 21:18 [PATCH 18/18] flag parameters: check magic constants Ulrich Drepper
2008-05-13 3:13 ` Andrew Morton
2008-05-13 3:45 ` David Miller
2008-05-13 3:54 ` Ulrich Drepper
2008-05-13 4:01 ` Andrew Morton
2008-05-13 4:02 ` David Miller
2008-05-13 4:21 ` Ulrich Drepper [this message]
2008-05-13 4:39 ` David Miller
2008-05-13 5:04 ` Andrew Morton
2008-05-13 5:10 ` Ulrich Drepper
2008-05-13 5:19 ` Andrew Morton
2008-05-13 5:42 ` Ulrich Drepper
2008-05-14 4:43 ` Andrew Morton
2008-05-23 5:22 ` Andrew Morton
2008-05-23 14:31 ` Ulrich Drepper
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=48291749.1060400@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--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.