From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fs: ext4 write: return file len on success
Date: Tue, 17 Feb 2015 15:38:39 -0700 [thread overview]
Message-ID: <54E3C2EF.1000106@wwwdotorg.org> (raw)
In-Reply-To: <1424183512-18290-1-git-send-email-p.marczak@samsung.com>
On 02/17/2015 07:31 AM, Przemyslaw Marczak wrote:
> After rework of the file system API, the size of ext4
> write was missed. This causes printing unreliable write
> size at the end of the file system write operation.
Tested-by: Stephen Warren <swarren@nvidia.com>
This fixes the issue I mentioned in the DFU-related thread.
next prev parent reply other threads:[~2015-02-17 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 14:31 [U-Boot] [PATCH] fs: ext4 write: return file len on success Przemyslaw Marczak
2015-02-17 22:38 ` Stephen Warren [this message]
2015-02-20 10:40 ` Przemyslaw Marczak
2015-03-06 15:46 ` [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=54E3C2EF.1000106@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox