From: Przemyslaw Marczak <p.marczak@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fs: ext4 write: return file len on success
Date: Fri, 20 Feb 2015 11:40:50 +0100 [thread overview]
Message-ID: <54E70F32.1080704@samsung.com> (raw)
In-Reply-To: <1424183512-18290-1-git-send-email-p.marczak@samsung.com>
Hello,
On 02/17/2015 03:31 PM, 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.
>
> Signed-off-by: Przemyslaw Marczak <p.marczak@samsung.com>
> Cc: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
> Cc: Lukasz Majewski <l.majewski@samsung.com>
> Cc: Simon Glass <sjg@chromium.org>
> ---
> fs/ext4/ext4_write.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/ext4/ext4_write.c b/fs/ext4/ext4_write.c
> index f7c52cc..fbc4c4b 100644
> --- a/fs/ext4/ext4_write.c
> +++ b/fs/ext4/ext4_write.c
> @@ -1000,10 +1000,13 @@ int ext4_write_file(const char *filename, void *buf, loff_t offset,
> }
> ext4fs_close();
>
> + *actwrite = len;
> +
> return 0;
>
> fail:
> ext4fs_close();
> + *actwrite = 0;
>
> return -1;
> }
>
Tom, this patch is a fix for write command.
Could you please, take it into the master?
Then I will not resend it with other patch set,
because it's actually independent.
Best regards,
--
Przemyslaw Marczak
Samsung R&D Institute Poland
Samsung Electronics
p.marczak at samsung.com
next prev parent reply other threads:[~2015-02-20 10:40 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
2015-02-20 10:40 ` Przemyslaw Marczak [this message]
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=54E70F32.1080704@samsung.com \
--to=p.marczak@samsung.com \
--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.