From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44286) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHrrF-0001NJ-St for qemu-devel@nongnu.org; Wed, 31 Oct 2018 10:52:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gHrrF-0006gV-65 for qemu-devel@nongnu.org; Wed, 31 Oct 2018 10:52:33 -0400 From: Markus Armbruster References: <20181031053920.7565-1-famz@redhat.com> Date: Wed, 31 Oct 2018 15:51:53 +0100 In-Reply-To: <20181031053920.7565-1-famz@redhat.com> (Fam Zheng's message of "Wed, 31 Oct 2018 13:39:20 +0800") Message-ID: <87va5irwxi.fsf@dusky.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH v2] file-posix: Use error API properly List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng Cc: qemu-devel@nongnu.org, Kevin Wolf , armbru@redhat.com, qemu-block@nongnu.org, Max Reitz Fam Zheng writes: > Use error_report for situations that affect user operation (i.e. we're > actually returning error), and warn_report/warn_report_err when some > less critical error happened but the user operation can still carry on. > > For raw_normalize_devicepath, add Error parameter to propagate to > its callers. > > Suggested-by: Markus Armbruster > Signed-off-by: Fam Zheng Reviewed-by: Markus Armbruster Kevin, if you'd prefer this to go through my tree, let me know.