lkml.org 
[lkml]   [2003]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: Chaotic structure of the net headers?
From
   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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.043 / U:0.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site