Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

2015-12-20 Thread Ben Hutchings
Control: tag -1 - patch On Mon, 2015-12-21 at 12:17 +1030, Arthur Marsh wrote: > Package: src:linux > Version: 4.3.3-2 > Severity: normal > Tags: upstream patch > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >    * What led up to the

Processed: Re: Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

2015-12-20 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - patch Bug #808567 [src:linux] linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream Removed tag(s) patch. -- 808567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808567 Debian Bug Tracking System

Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

2015-12-20 Thread Arthur Marsh
This is no way an acceptable patch. The driver needs to be converted properly to the Linux 2.6+ device model, instead of adding further kluges to it. Ben. Thanks, that patch wasn't provided by me. The old driver just broke during other updates and that patch was provided as a workaround

Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

2015-12-20 Thread Ben Hutchings
On Mon, 2015-12-21 at 12:56 +1030, Arthur Marsh wrote: > > This is no way an acceptable patch.  The driver needs to be converted > > properly to the Linux 2.6+ device model, instead of adding further > > kluges to it. > > > > Ben. > > > > Thanks, that patch wasn't provided by me. The old driver

Bug#808567: linux-image-4.3.0-1-686-pae: eata module required for DPT SCSI adapter fails, lack of response upstream

2015-12-20 Thread Arthur Marsh
Package: src:linux Version: 4.3.3-2 Severity: normal Tags: upstream patch Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Attempting to load a kernel later than 4.2.0. * What exactly did you do (or not do)