On Thu, Feb 05, 2004 at 01:31:45PM -0500, Tillier, Fabian wrote: > > Are you suggesting that if there is any abstraction, the code will never > be accepted? Or rather that the abstraction better be correct? I'm > hoping for the latter, however please clarify. The kernel has its own abstractions that seem to be working quite well for all different types of platforms. There is no need for you to create your own, just for a driver subsystem. If you have found any problems with the current locks please let the entire kernel community benefit from your changes, and not relegate them to a infiniband-only section of the kernel. So yes, if you add your own versions of spinlocks and atomic_t types, your code will be rejected, among other things :) thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Prev by Date: RE: [Infiniband-general] Getting an Infiniband access layer in the Linux kernel
- Next by Date: RE: [Infiniband-general] Getting an Infiniband access layer in the linux kernel
- Previous by thread: RE: [Infiniband-general] Getting an Infiniband access layer in the Linux kernel
- Next by thread: Re: [Infiniband-general] Getting an Infiniband access layer in theLinux kernel
- Indexes:[Main][Thread]