>Someone had a go at "making 2.5 compile" without taking Alan's 2.4
>changes. It went into Linus tree. It got subsequently reverted
>because of the reasons I outlined in my previous mail.
Maybe you are thinking of the patches that I posted a
while ago that included an update to some locking changes for
a bunch of the scsi drivers. Alan spoke up and said that
I should not apply the NCR53C80 part of those patches because
I had made a mistake and becuase there was a newer driver in 2.4,
and provided some tips on porting the 2.4 driver. I immediately
said I would follow Alan's advice and not submit patches
based on the old NCR53C80-based drivers.
Maybe you were thinking of some other event when you
said "I believe changes to NCR53c80 were recently reverted back because
these 'fixes' lead to massive data corruption." If so, I would be
interested in hearing about it.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/