Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751374AbWB1PWq (ORCPT ); Tue, 28 Feb 2006 10:22:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751493AbWB1PWq (ORCPT ); Tue, 28 Feb 2006 10:22:46 -0500 Received: from mail.dvmed.net ([216.237.124.58]:8331 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S1751374AbWB1PWp (ORCPT ); Tue, 28 Feb 2006 10:22:45 -0500 Message-ID: <44046AC2.1060002@pobox.com> Date: Tue, 28 Feb 2006 10:22:42 -0500 From: Jeff Garzik User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jens Axboe CC: Hannes Reinecke , Linux Kernel , linux-ide@vger.kernel.org Subject: Re: [PATCH] Fixup ahci suspend / resume References: <44045FB1.5040408@suse.de> <440468DB.5060605@pobox.com> <20060228151928.GC24981@suse.de> In-Reply-To: <20060228151928.GC24981@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 958 Lines: 25 Jens Axboe wrote: > Upstream 2.6.x certainly _does_ care about suspend/resume! To me, this > patch seems simple enough to be included. It's little more than > splitting the register init out form the port_stop/start functions and > calling them on resume/suspend appropriately. Upstream _libata_ doesn't care much about suspend/resume. Officially, its a work in progress with major pieces -- your patch and ACPI -- still missing. Further, good improvements covering some of the changes in Hannes' patch are already in #upstream. Thus, it's more work than its worth to care about the patch as-is. It should be redone against #upstream, which is where all suspend/resume development is occurring. Jeff - 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/