From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Tue, 12 Apr 2016 11:32:40 -0600 Subject: [U-Boot] [PATCH] gunzip.c: use block layer for writes In-Reply-To: <20160412172135.GE13577@bill-the-cat> References: <1460413297-16640-1-git-send-email-eric@nelint.com> <570D2614.3020504@wwwdotorg.org> <570D2DEF.1040201@nelint.com> <20160412172135.GE13577@bill-the-cat> Message-ID: <570D3138.4080800@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 04/12/2016 11:21 AM, Tom Rini wrote: > On Tue, Apr 12, 2016 at 10:18:39AM -0700, Eric Nelson wrote: >> Thanks Stephen, >> >> On 04/12/2016 09:45 AM, Stephen Warren wrote: >>> On 04/11/2016 04:21 PM, Eric Nelson wrote: >>>> Call blk_dwrite to ensure that the block cache is notified >>>> if enabled and remove build breakage when CONFIG_BLK is enabled. >>> >>> Reviewed-by: Stephen Warren >>> >>> You probably wanted to Cc whichever maintainer will apply this though. >>> Hopefully they'll see it in patchwork. >> >> I'm not sure who that might be and I included everyone on >> the output of get_maintainer.pl. >> >> Tom's the last one to commit and comment on the gzwrite piece >> of code, so perhaps it's him. > > Indeed, last resort is me :) I suppose the top of my head question is, > do we have some gunzip tests that test.py will kick off? I don't believe we do for the command. IIRC there's a sandbox test for the core gunzip routine itself, but not the gzwrite command that uses it.