Re: [Infiniband-general] Getting an Infiniband access layer in the linux kernel

[Greg KH]

On Thu, Feb 05, 2004 at 12:16:17PM -0800, Woodruff, Robert J wrote:
> I think that we tried to isolate a lot of these kernel calls into
> one library, the component library, so that when the kernel APIs change,
> which seems to happen every release, we only have to change the code 
> in one spot. 

Then get your code into the kernel tree, and you will not have to worry
about this "problem".  Remember, that is what we are talking about here.
If you want to keep your "compatibility" library in your out-of-tree
code, that's fine with me, I don't care.

It's when you try to push that into the main kernel tree that I start to
care.

> Are there any other examples of drivers that isolate kernel specific
> calls to one module or file of their code to ease portability between
> different revisions of the kernel ? If not, maybe they should look at
> what we have done, it might save them some headaches in the future. 

No, that is not how Linux kernel development is done.  Come on people,
do your research...

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/