[lkml]   [2008]   [Apr]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ANN] WiMAX stack and drivers for Intel WiMAX Link 5050

Inaky Perez-Gonzalez <inaky-VuQAYsv1563Yd54FQh9/> writes:
> There is almost no inlining because each X only does stuff from itself. If
> there is a need for inlined stuff (I missed it) it should go to one of the
> header files --internal or external.

Inlining gets more and more discouraged. Also longer term I would
expect that gcc will do inlining over files anyways (it already supports
that, but needs special support in the Makefiles which the kernel
doesn't have). So even with inlining you wouldn't need to merge files
or move code into headers.

> version: I anticipate the wimax API exported to user space is
> going to undergo a lot of changes while we all agree on what
> is the best interface. Because things might break, I want to
> make sure user space stuff can detect that and fail cleanly.
> Hence the versioning.

It's still a bad way to do that (I agree with Stephen on that).
Was also always a mess on wireless.

If you don't want expandable TLAs another better alternative to
versions is ext2 style compatible/incompatible feature bitmaps.


 \ /
  Last update: 2008-04-09 08:39    [W:0.059 / U:1.848 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site