From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: How to add/drop SCSI drives from within the driver? Date: Thu, 16 Dec 2004 14:41:34 +0000 Message-ID: <1103208085.21806.1.camel@localhost.localdomain> References: <60807403EABEB443939A5A7AA8A7458B7F5071@otce2k01.adaptec.com> <1102536081.4218.0.camel@localhost.localdomain> <20041215072453.GB17274@lists.us.dell.com> <1103136559.5232.1.camel@mulgrave> <20041215213001.GA9284@lists.us.dell.com> <1103190852.4136.12.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1103190852.4136.12.camel@laptopd505.fenrus.org> Sender: linux-kernel-owner@vger.kernel.org To: Arjan van de Ven Cc: Matt Domsch , James Bottomley , "Salyzyn, Mark" , "Bagalkote, Sreenivas" , brking@us.ibm.com, Linux Kernel Mailing List , SCSI Mailing List , bunk@fs.tum.de, Andrew Morton , "Ju, Seokmann" , "Doelfel, Hardy" , "Mukker, Atul" List-Id: linux-scsi@vger.kernel.org On Iau, 2004-12-16 at 09:54, Arjan van de Ven wrote: > I'm strongly against adding this. The reason for that is that once an > ioctl is added, it realistically will and can never go away. > LSI is free to have their own fork and give that to dell; but they > should and could have known that it wasn't going to fly. (same I guess > for adaptec ioctls). The companies who then commit to some schedule > realize they take a huge risk, but that is no reason to foul up the > kernel more. I agree. I'd like to see an agreed standard interface for dropping and managing physical volumes and drives, as well as a standard interface for dropping/managing logical volumes.