Re: LLDD: scatterlists only?

2005-08-14 Thread Mike Christie
Douglas Gilbert wrote: James Bottomley wrote: On Sun, 2005-08-14 at 16:24 -0700, Luben Tuikov wrote: Did someone have a patch or was there a talk that SCSI Core is moving towards sending _only_ scatterlists down to LLDDs? (effectively BUG_ON(!cmd->use_sg)) Yes, you can already see the be

Re: LLDD: scatterlists only?

2005-08-14 Thread Douglas Gilbert
James Bottomley wrote: > On Sun, 2005-08-14 at 16:24 -0700, Luben Tuikov wrote: > >>Did someone have a patch or was there a talk >>that SCSI Core is moving towards sending _only_ scatterlists >>down to LLDDs? (effectively BUG_ON(!cmd->use_sg)) > > > Yes, you can already see the beginnings in th

Re: [GIT PATCH] scsi bug fixes for 2.6.13

2005-08-14 Thread Guennadi Liakhovetski
On Sun, 14 Aug 2005, James Bottomley wrote: > OK, why don't we do this. Instead of having me trawl through the trees > looking for the correct patch to reverse, why don't you attach it in an > email and I'll try to get it in to 2.6.13? Looks like just reverting that patch is not enough. More in

Re: [PATCH] add transport class symlink to device object

2005-08-14 Thread Matthew Wilcox
On Sun, Aug 14, 2005 at 11:25:25PM +0100, Russell King wrote: > On Sun, Aug 14, 2005 at 04:02:31PM +0100, Matthew Wilcox wrote: > > Last time I tried to do something like this, it fell over with > > multi-function serial ports. Look at this example: > > > > # ls -l /sys/class/tty/ttyS*/device | c

LLDD: scatterlists only?

2005-08-14 Thread Luben Tuikov
Hi, Did someone have a patch or was there a talk that SCSI Core is moving towards sending _only_ scatterlists down to LLDDs? (effectively BUG_ON(!cmd->use_sg)) Luben - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More

Re: LLDD: scatterlists only?

2005-08-14 Thread Luben Tuikov
--- James Bottomley <[EMAIL PROTECTED]> wrote: > On Sun, 2005-08-14 at 16:24 -0700, Luben Tuikov wrote: > > Did someone have a patch or was there a talk > > that SCSI Core is moving towards sending _only_ scatterlists > > down to LLDDs? (effectively BUG_ON(!cmd->use_sg)) > > Yes, you can already

Re: LLDD: scatterlists only?

2005-08-14 Thread James Bottomley
On Sun, 2005-08-14 at 16:24 -0700, Luben Tuikov wrote: > Did someone have a patch or was there a talk > that SCSI Core is moving towards sending _only_ scatterlists > down to LLDDs? (effectively BUG_ON(!cmd->use_sg)) Yes, you can already see the beginnings in the -mm tree. Jens is maintaining a

LLDD: scatterlists only?

2005-08-14 Thread Luben Tuikov
Hi, Did someone have a patch or was there a talk that SCSI Core is moving towards sending _only_ scatterlists down to LLDDs? (effectively BUG_ON(!cmd->use_sg)) Luben - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] Mor

Re: [PATCH] add transport class symlink to device object

2005-08-14 Thread Russell King
On Sun, Aug 14, 2005 at 04:02:31PM +0100, Matthew Wilcox wrote: > On Sat, Aug 13, 2005 at 02:39:56PM -0700, Greg KH wrote: > > Heh, I already have a patch like this pending for 2.6.14 at: > > > > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/driver-link-devic

Re: [GIT PATCH] scsi bug fixes for 2.6.13

2005-08-14 Thread Guennadi Liakhovetski
On Sun, 14 Aug 2005, James Bottomley wrote: > On Sun, 2005-08-14 at 21:33 +0200, Guennadi Liakhovetski wrote: > > Just to make sure everyone agrees on this - there's currently a know bug > > in dc395x with highmem reported by Pierre Ossman in thread "Kernel panic > > with dc395x in 2.6.12.2" on

[PATCH] correct transport class abstraction to work outside SCSI

2005-08-14 Thread James Bottomley
I recently tried to construct a totally generic transport class and found there were certain features missing from the current abstract transport class. Most notable is that you have to hang the data on the class_device but most of the API is framed in terms of the generic device, not the class_de

Re: [GIT PATCH] scsi bug fixes for 2.6.13

2005-08-14 Thread James Bottomley
On Sun, 2005-08-14 at 21:33 +0200, Guennadi Liakhovetski wrote: > Just to make sure everyone agrees on this - there's currently a know bug > in dc395x with highmem reported by Pierre Ossman in thread "Kernel panic > with dc395x in 2.6.12.2" on linux-scsi. It is also trivial to reproduce on > non

[PATCH] add ability to deny binding to SPI transport class

2005-08-14 Thread James Bottomley
This patch is necessary if we begin exposing underlying physical disks (which can attach to the SPI transport class) of the hardware RAID cards, since we don't want any SPI parameters binding to the raid devices. James --- a/drivers/scsi/scsi_transport_spi.c +++ b/drivers/scsi/scsi_transport_spi.

Re: [GIT PATCH] scsi bug fixes for 2.6.13

2005-08-14 Thread Guennadi Liakhovetski
Hi On Thu, 4 Aug 2005, James Bottomley wrote: > This is my (hopefully final) collection of safe driver updates and bug > fixes for 2.6.13. Just to make sure everyone agrees on this - there's currently a know bug in dc395x with highmem reported by Pierre Ossman in thread "Kernel panic with dc39

Re: [PATCH] add transport class symlink to device object

2005-08-14 Thread Matthew Wilcox
On Sat, Aug 13, 2005 at 02:39:56PM -0700, Greg KH wrote: > Heh, I already have a patch like this pending for 2.6.14 at: > > http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-01-driver/driver-link-device-and-class.patch Last time I tried to do something like this, it fel

RE: [PATCH] add transport class symlink to device object

2005-08-14 Thread James Bottomley
On Sun, 2005-08-14 at 08:42 -0400, [EMAIL PROTECTED] wrote: > I'll trust that James B's fix resolves things. Thought my testing was > straight-forward and ok. Guess not. Humbled again as a mere mortal in > the world of sysfs and transport/container logic... :) Well ... I confidently predict that y

RE: [PATCH] add transport class symlink to device object

2005-08-14 Thread James . Smart
I'll trust that James B's fix resolves things. Thought my testing was straight-forward and ok. Guess not. Humbled again as a mere mortal in the world of sysfs and transport/container logic... :) Anyway, the last item that needs discussion is what name should the symlink have ? Here's a few points