Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757923AbYBTGdf (ORCPT ); Wed, 20 Feb 2008 01:33:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754487AbYBTGdZ (ORCPT ); Wed, 20 Feb 2008 01:33:25 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:37983 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753495AbYBTGdY (ORCPT ); Wed, 20 Feb 2008 01:33:24 -0500 Date: Tue, 19 Feb 2008 22:20:43 -0800 From: Greg KH To: Alan Stern Cc: Pavel Machek , kernel list , Linux-pm mailing list Subject: Re: Status of storage autosuspend Message-ID: <20080220062043.GA22308@kroah.com> References: <20080218222014.GB31201@elf.ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1115 Lines: 28 On Mon, Feb 18, 2008 at 10:19:11PM -0500, Alan Stern wrote: > On Mon, 18 Feb 2008, Pavel Machek wrote: > > > > Should we ignore this issue and submit the patches anyway? > > > > I think you should. "Easy" (and clean) solution to that issue is to > > just return -EPERM from SG_IOCTL if autosuspend is configured in ;-). > > :-) > > Okay, I'll update the patches to 2.6.25-rc2 and submit them in a few > days. (Actually the SCSI patch has to go in first and the usb-storage > patch afterward, which will probably cause it to be delayed one kernel > version. I don't know any good way to handle these cross-subsystem > updates...) Push the usb-storage one through the scsi tree as well. The subsystem maintainers handle this kind of thing all the time (for example, a sysfs feature is about to go in through the ocfs tree for this very reason.) thanks, greg k-h -- 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/