On Fri, 27 Apr 2007, Adrian Bunk wrote: > This patch removes kernel 2.4 code. > > Signed-off-by: Adrian Bunk <bunk@xxxxxxxxx> > > --- > > This patch has been sent on: > - 26 Mar 2007 > > drivers/scsi/nsp32.c | 109 +++++-------------------------------------- > 1 file changed, 13 insertions(+), 96 deletions(-) > > --- linux-2.6.21-rc4-mm1/drivers/scsi/nsp32.c.old 2007-03-25 20:27:34.000000000 +0200 > +++ linux-2.6.21-rc4-mm1/drivers/scsi/nsp32.c 2007-03-25 20:31:59.000000000 +0200 > @@ -49,10 +49,6 @@ > #include <scsi/scsi_host.h> > #include <scsi/scsi_ioctl.h> > > -#if (LINUX_VERSION_CODE < KERNEL_VERSION(2,6,0)) > -# include <linux/blk.h> > -#endif > - i'm curious about the rules for removing code like this. in the case of drivers, isn't it possible that some driver source could be relevant for both the 2.4 and 2.6 kernel source tree, and simply uses that kind of preprocessor check to make sure it's being compiled appropriately? or are you doing something more sophisticated than simply checking the kernel version being tested? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://fsdev.net/wiki/index.php?title=Main_Page ======================================================================== - To unsubscribe from this list: 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
