[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrX9GZmWnfkm-CwKW-2mPvRbNcRaY6tUY=8e0THsPBKMcA@mail.gmail.com>
Date: Tue, 21 Apr 2015 18:58:58 -0700
From: Andy Lutomirski <luto@...capital.net>
To: James Bottomley <James.Bottomley@...senpartnership.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Kweh, Hock Leong" <hock.leong.kweh@...el.com>,
Matt Fleming <matt@...eblueprint.co.uk>,
Ming Lei <ming.lei@...onical.com>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
Sam Protsenko <semen.protsenko@...aro.org>,
Peter Jones <pjones@...hat.com>,
Roy Franz <roy.franz@...aro.org>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH v4 2/2] efi: an sysfs interface for user to update efi firmware
On Tue, Apr 21, 2015 at 6:21 PM, James Bottomley
<James.Bottomley@...senpartnership.com> wrote:
> Andy, just on the misc device idea, what about triggering the capsule
> update from close()? In theory close returns an error code (not sure if
> most tools actually check this, though). That means we can do the write
> in chunks but pass it in atomically on the close and cat will work
> (provided it checks the return code of close).
I thought about this but IIRC cat doesn't check the return value from close.
--Andy
>
> James
>
>
--
Andy Lutomirski
AMA Capital Management, LLC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists