![]() | ||||||||||
Messages in this thread |
On Wed, 09 Apr 2003 11:34:01 -0600 "Justin T. Gibbs" <gibbs@scsiguy.com> wrote: > > On Mer, 2003-04-09 at 02:21, Chuck Ebbert wrote: > >> And your code goes for long periods of time without merging good fixes, > >> like this one (from 2.4.20): > > > > Which is one reason Justin's patches don't get merged. They are giant > > changes which back out other clear corrections. > > This tells me two things: > > 1) You don't trust maintainers. If a maintainer can't make large changes, > who can? > > 2) When a maintainer makes a mistake (fails to integrate a good change, > or introduces a bug), the maintainers changes are simply dropped rather > then notify (either politely or not I don't much care) the maintainer > of his/her mistake. > > Neither of the above applied to integration of the aic79xx driver into > the 2.4.X tree, but it still took something like 8 months. > > There must be a better way. As I am probably one of the victims of these differing opinions, can anyone tell me where to get a really-known-to-work aic-driver for 2.4? I am experiencing zapping-black events while reading from a SDLT drive (writing to it does fine). Short hardware story: 02:03.0 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01) 02:03.1 SCSI storage controller: Adaptec AIC-7899P U160/m (rev 01) Host: scsi0 Channel: 00 Id: 08 Lun: 00 Vendor: IBM Model: IC35L073UWDY10-0 Rev: S21E Type: Direct-Access ANSI SCSI revision: 03 Host: scsi1 Channel: 00 Id: 02 Lun: 00 Vendor: QUANTUM Model: SDLT320 Rev: 3838 Type: Sequential-Access ANSI SCSI revision: 02 Any hints welcome Regards, Stephan - 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/ | |||||||||
| Last update: 2005-03-22 12:34 [from the cache] ©2003-2008 | ||||||||||