Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 20 Jun 2002 14:36:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 20 Jun 2002 14:36:05 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:58896 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Thu, 20 Jun 2002 14:36:03 -0400 Date: Thu, 20 Jun 2002 11:36:25 -0700 (PDT) From: Linus Torvalds To: Patrick Mansfield cc: Andries Brouwer , Martin Schwenke , Kurt Garloff , Linux kernel list , Linux SCSI list , Patrick Mochel Subject: Re: [PATCH] /proc/scsi/map In-Reply-To: <20020620105233.A5506@eng2.beaverton.ibm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 973 Lines: 27 On Thu, 20 Jun 2002, Patrick Mansfield wrote: > > With Mike Sullivan'a patch for SCSI driverfs support: > > http://marc.theaimsgroup.com/?l=linux-scsi&m=102434655912858&w=2 Interesting, it does seem to set up most of the obvious stuff. SCSI people, how does that patch look to you? Apparently it does everything the scsimap thing does, in a way that is certainly acceptable to me. I personally think that the biggest problem with driverfs is it's lack of a 2.4.x counterpart. Although the filesystem itself should be fairly easy to port, moving around all the pci device structure members etc in order to embed "struct device" into the PCI structure sounds like something you definitely don't want to do in 2.4.x. Linus - 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/