From: "David S. Miller" <davem@redhat.com>
To: Rod.VanMeter@nokia.com
Cc: bunk@fs.tum.de, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Chaotic structure of the net headers?
Date: Wed, 05 Mar 2003 15:03:44 -0800 (PST) [thread overview]
Message-ID: <20030305.150344.50145701.davem@redhat.com> (raw)
In-Reply-To: <1046905834.17778.400.camel@localhost.localdomain>
From: Rod Van Meter <Rod.VanMeter@nokia.com>
Date: 05 Mar 2003 15:10:35 -0800
Does it make sense to have two forms, one kernel, one user? I haven't
e.g. followed the desired include chain. If we wanted to merge the
uses, the former form and include location would probably have to be
used.
I've been looking into this. There are a *few* things missing from the
2292 support. AFAICT, it's just a handful of functions/macros for
manipulating option headers that need to be added.
Actually forget all my comments, GLIBC headers are where
the advanced socket API requirements for headers should
be applied.
And since this is only used in the kernel, there is no need
for the NEXTHDR_* if it trully just duplicates the IPPROTO_*
defines.
I'm willing to accept a cleanup patch of this nature, sure.
next prev parent reply other threads:[~2003-03-05 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 22:54 Chaotic structure of the net headers? Adrian Bunk
2003-03-05 22:39 ` David S. Miller
2003-03-05 23:10 ` Rod Van Meter
2003-03-05 23:03 ` David S. Miller [this message]
2003-03-05 23:53 ` Richard Guy Briggs
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=20030305.150344.50145701.davem@redhat.com \
--to=davem@redhat.com \
--cc=Rod.VanMeter@nokia.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 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 NNTP newsgroup(s).