public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/2] fs: implement size/fatsize/ext4size
Date: Tue, 17 Jun 2014 10:57:19 +0200	[thread overview]
Message-ID: <20140617105719.2464a4a4@amdc2363> (raw)
In-Reply-To: <1402512447-31897-1-git-send-email-swarren@wwwdotorg.org>

Hi Stephen,

> From: Stephen Warren <swarren@nvidia.com>
> 
> These commands may be used to determine the size of a file without
> actually reading the whole file content into memory. This may be used
> to determine if the file will fit into the memory buffer that will
> contain it. In particular, the DFU code will use it for this purpose
> in the next commit.
> 
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> v2: New patch

Stephen thanks for the patch.

Acked-by: Lukasz Majewski <l.majewski@samsung.com>

Test HW: Trats2 (Exynos4412):
Tested-by: Lukasz Majewski <l.majewski@samsung.com>

Organizational issue:

File systems don't have their own trees, so if Tom or Marek don't mind
I would like to take this patch to -dfu tree.

Justification:
This patch was written solely for fixing flaws of DFU, so I think that
it is appropriate to take it to -dfu tree and in this way provide
consistency with the following DFU patch.



-- 
Best regards,

Lukasz Majewski

Samsung R&D Institute Poland (SRPOL) | Linux Platform Group

  parent reply	other threads:[~2014-06-17  8:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 18:47 [U-Boot] [PATCH V2 1/2] fs: implement size/fatsize/ext4size Stephen Warren
2014-06-11 18:47 ` [U-Boot] [PATCH V2 2/2] dfu: fix some issues with reads/uploads Stephen Warren
2014-06-17  8:59   ` Lukasz Majewski
2014-06-20  7:53   ` Lukasz Majewski
2014-06-17  8:57 ` Lukasz Majewski [this message]
2014-06-18 17:40   ` [U-Boot] [PATCH V2 1/2] fs: implement size/fatsize/ext4size Tom Rini
2014-06-20  7:53 ` Lukasz Majewski

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=20140617105719.2464a4a4@amdc2363 \
    --to=l.majewski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox