From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH v6 0/2] Enable capsule loader interface for efi firmware updating Date: Sat, 3 Oct 2015 11:05:39 +0200 Message-ID: <20151003090539.GC11942@pd.tnic> References: <1443733554-22743-1-git-send-email-hock.leong.kweh@intel.com> <20151002173704.GD16538@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Matt Fleming , Greg Kroah-Hartman , "Ong, Boon Leong" , LKML , "linux-efi@vger.kernel.org" , Sam Protsenko , Peter Jones , Andy Lutomirski , Roy Franz , James Bottomley , Linux FS Devel , "Fleming, Matt" To: "Kweh, Hock Leong" Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Oct 03, 2015 at 03:18:41AM +0000, Kweh, Hock Leong wrote: > > What does the error case look like? A standard glibc message about > > write(2) failing? > > > > Any upload fail error like -ENOMEM, -EINVAL, -EIO as well as error returned > by efi_capsule_update() API. All I'm asking is, how does the user know that the upload didn't succeed? -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.