From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (bilbo.ozlabs.org [103.22.144.67]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 40D0bG2hKLzF1pr for ; Sun, 1 Apr 2018 01:04:10 +1100 (AEDT) In-Reply-To: <20180326150233.23089-1-npiggin@gmail.com> To: Nicholas Piggin , linuxppc-dev@lists.ozlabs.org From: Michael Ellerman Cc: Nicholas Piggin Subject: Re: powerpc/powernv/nvram: opal_nvram_write handle unknown OPAL errors Message-Id: <40D0bF6VVsz9s3v@ozlabs.org> Date: Sun, 1 Apr 2018 01:04:09 +1100 (AEDT) List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2018-03-26 at 15:02:33 UTC, Nicholas Piggin wrote: > opal_nvram_write currently just assumes success if it encounters an > error other than OPAL_BUSY or OPAL_BUSY_EVENT. Have it return -EIO > on other errors instead. > > Signed-off-by: Nicholas Piggin > Reviewed-by: Vasant Hegde > Acked-by: Stewart Smith Applied to powerpc next, thanks. https://git.kernel.org/powerpc/c/741de617661794246f84a21a02fc5e cheers