This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue May 21 16:41:11 2024 Delivery-date: Tue, 03 Oct 2006 12:52:20 +0000 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932101AbWJCMvq (ORCPT ); Tue, 3 Oct 2006 08:51:46 -0400 Received: from odyssey.analogic.com ([204.178.40.5]:32531 "EHLO odyssey.analogic.com") by vger.kernel.org with ESMTP id S932096AbWJCMvp convert rfc822-to-8bit (ORCPT ); Tue, 3 Oct 2006 08:51:45 -0400 Received: from chaos.analogic.com ([10.112.50.11]) by phoenix.analogic.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 3 Oct 2006 08:51:41 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Received: from chaos.analogic.com (localhost [127.0.0.1]) by chaos.analogic.com (8.12.11/8.12.11) with ESMTP id k93Cpa9B021225; Tue, 3 Oct 2006 08:51:36 -0400 Received: (from linux-os@localhost) by chaos.analogic.com (8.12.11/8.12.11/Submit) id k93CpaQr021224; Tue, 3 Oct 2006 08:51:36 -0400 X-OriginalArrivalTime: 03 Oct 2006 12:51:41.0643 (UTC) FILETIME=[AC7089B0:01C6E6EA] content-class: urn:content-classes:message Subject: Re: error to be returned while suspended Date: Tue, 3 Oct 2006 08:51:36 -0400 Message-Id: In-Reply-To: <200610031323.00547.oliver@neukum.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: error to be returned while suspended Thread-Index: Acbm6qyNV/DrBjZpRcmVETpmMJJK0A== References: <200610031323.00547.oliver@neukum.org> From: "linux-os \(Dick Johnson\)" To: "Oliver Neukum" Cc: Reply-To: "linux-os \(Dick Johnson\)" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 3 Oct 2006, Oliver Neukum wrote: > Hi, > > which error should a character device return if a read/write cannot be > serviced because the device is suspended? Shouldn't there be an error > code specific to that? > > Regards > Oliver The de-facto error codes were created long before one could "suspend" a device, so there isn't a ESUSP code. However, I suggest EIO or EBUSY unless you want to define an ESUSP and get it accepted by the POSIX committee. Cheers, Dick Johnson Penguin : Linux version 2.6.16.24 on an i686 machine (5592.72 BogoMips). New book: http://www.AbominableFirebug.com/ _  **************************************************************** The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them. Thank you. - 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/