> > On Sun, 2005-07-10 at 18:15 -0600, Moore, Eric Dean wrote: > > I'd rather you not kill linux_compat.h file. > > I use this file for compatibility of driver source > > across various kernel versions. I provide our > > customers with driver builds containing single source > > which needs to compile in kernels 2.6.5( e.g. SLES9), > > 2.6.8 (e.g. RHEL4), and 2.6.11 ( e.g. SuSE 9.3 Pro). > > It is the general policy that the source in the latest linux > kernel only > supports that kernel. You can certainly keep a compat header for your > customers, but what is in kernel.org should be clean for that > version of > the kernel. Thanks for that info. But Id rather have same files in our maintained driver, and whats in the kernel tree. > > > If you look at our 3.02.18 driver source I submitted to SuSE > > for SLES9 SP2, you will see this file is about 3K bytes of > > compatibility. > > Is the 3.02.18 code generally available now? Can it be cleaned up for > submission to 2.6.13? > The 3.02.18 driver and the driver in kernel tree are totally different drivers. One thing is 3.02.18 has SAS support, and the kernel tree doesn't. Id wish kernel folks would take our SAS drivers. Eric Moore - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
