Re: Chaotic structure of the net headers?

["David S. Miller" <davem@xxxxxxxxxx>]

   From: Rod Van Meter <Rod.VanMeter@xxxxxxxxx>
   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.