Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932110AbVLHN51 (ORCPT ); Thu, 8 Dec 2005 08:57:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932111AbVLHN50 (ORCPT ); Thu, 8 Dec 2005 08:57:26 -0500 Received: from magic.adaptec.com ([216.52.22.17]:17846 "EHLO magic.adaptec.com") by vger.kernel.org with ESMTP id S932105AbVLHN5Z convert rfc822-to-8bit (ORCPT ); Thu, 8 Dec 2005 08:57:25 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT Subject: RE: RFC: ACPI/scsi/libata integration and hotswap Date: Thu, 8 Dec 2005 08:57:15 -0500 Message-ID: <547AF3BD0F3F0B4CBDC379BAC7E4189F01EE9D15@otce2k03.adaptec.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: RFC: ACPI/scsi/libata integration and hotswap Thread-Index: AcX7/dUfJZsuMpkSTdKlpoJ2S4/AAwAAJYog From: "Salyzyn, Mark" To: "Christoph Hellwig" , "Matthew Garrett" Cc: , , , , Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 949 Lines: 21 Christoph Hellwig writes: > Why oh why do our chipset friends at intel have to fuck up > everything they can? I wish they'd learn a lesson or two from their cpu collegues. The patch doesn't look like too much of a hack, pretty clean implementation in support of a hot-swap of an adapter using ACPI hooks. It is not specific to x86 platforms. I'd prefer that it looked more like a suspend/resume interface rather than a raw ACPI event. There needs to be a power management interface to SCSI and to the LLD's in support of hot-swap of PCI attached devices. Otherwise you are asking for the driver to be blindsided on any platform that supports this necessary service feature. Sincerely -- Mark Salyzyn - 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/