All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] gunzip.c: use block layer for writes
Date: Tue, 12 Apr 2016 11:32:40 -0600	[thread overview]
Message-ID: <570D3138.4080800@wwwdotorg.org> (raw)
In-Reply-To: <20160412172135.GE13577@bill-the-cat>

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 <swarren@nvidia.com>
>>>
>>> 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.

  reply	other threads:[~2016-04-12 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 22:21 [U-Boot] [PATCH] gunzip.c: use block layer for writes Eric Nelson
2016-04-12 16:45 ` Stephen Warren
2016-04-12 17:18   ` Eric Nelson
2016-04-12 17:21     ` Tom Rini
2016-04-12 17:32       ` Stephen Warren [this message]
2016-04-20 14:40 ` Simon Glass
2016-04-21 11:22 ` [U-Boot] " Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=570D3138.4080800@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.