From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dfu: fix: Add the absolute path to the file name for ext4 write operation
Date: Mon, 21 Jul 2014 10:27:05 -0600 [thread overview]
Message-ID: <53CD3F59.1060101@wwwdotorg.org> (raw)
In-Reply-To: <1405503532-6415-1-git-send-email-l.majewski@samsung.com>
On 07/16/2014 03:38 AM, Lukasz Majewski wrote:
> Commit 1151b7ac10b81ecbb has cleaned up read and write operations.
> Unfortunately, for correct operation the write for ext4 fs requires
> absolute patch.
> This patch fixes this case.
Shouldn't the user simply supply the absolute patch name as the entity
name? That's what I've been doing.
This way, it makes files in sub-directories look more natural; you'd
pass in e.g. /boot/zImage rather than boot/zImage, which looks like a
relative path.
next prev parent reply other threads:[~2014-07-21 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 9:38 [U-Boot] [PATCH] dfu: fix: Add the absolute path to the file name for ext4 write operation Lukasz Majewski
2014-07-21 16:27 ` Stephen Warren [this message]
2014-07-22 8:00 ` Lukasz Majewski
2014-07-22 14:24 ` Marek Vasut
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=53CD3F59.1060101@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