From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:38408) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuScA-0007WI-71 for qemu-devel@nongnu.org; Thu, 26 Jul 2012 14:16:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SuSc9-0006Pi-1h for qemu-devel@nongnu.org; Thu, 26 Jul 2012 14:16:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62930) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SuSc8-0006P8-Pm for qemu-devel@nongnu.org; Thu, 26 Jul 2012 14:16:44 -0400 Date: Thu, 26 Jul 2012 14:02:50 -0300 From: Luiz Capitulino Message-ID: <20120726140250.297936e5@doriath.home> In-Reply-To: <50117772.3080903@redhat.com> References: <1343127865-16608-1-git-send-email-pbonzini@redhat.com> <1343127865-16608-3-git-send-email-pbonzini@redhat.com> <501161A4.6000800@redhat.com> <5011650D.1050100@redhat.com> <20120726134925.5d9512b2@doriath.home> <50117772.3080903@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 02/47] qerror/block: introduce QERR_BLOCK_JOB_NOT_ACTIVE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Kevin Wolf , jcody@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com On Thu, 26 Jul 2012 18:59:30 +0200 Paolo Bonzini wrote: > Il 26/07/2012 18:49, Luiz Capitulino ha scritto: > > On Thu, 26 Jul 2012 17:41:01 +0200 > > Paolo Bonzini wrote: > > > >> Il 26/07/2012 17:26, Kevin Wolf ha scritto: > >>>> The DeviceNotActive error is not a particularly good match, add > >>>>> a separate one. > >>>>> > >>>>> Signed-off-by: Paolo Bonzini > >>> Luiz, what do you think about this one? It seems to contradict the idea > >>> of having only few error classes and free form error descriptions. > >> > >> I agree, but that's what we have to live with for now... > > > > Why don't you add QERR_INVALID_STATE then? > > Because I do want a meaningful error message. It's fine with me adding QERR_BLOCK_JOB_NOT_ACTIVE then, as you've said, it's what we have today.