From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] cmd_fat: add FAT write command
Date: Thu, 05 Jan 2012 17:23:54 +0100 [thread overview]
Message-ID: <20120105162354.F41151FD3DA@gemini.denx.de> (raw)
In-Reply-To: <1324431247-17998-1-git-send-email-dg77.kim@samsung.com>
Dear Donggeun Kim,
In message <1324431247-17998-1-git-send-email-dg77.kim@samsung.com> you wrote:
> Once CONFIG_FAT_WRITE is defined,
> users can invoke 'fatwrite' command that saves data in RAM as a FAT file.
>
> By removing variable of 'part_size' in fs/fat.c,
> compile error occurs when enabling FAT write feature.
> The variable should be declared only when CONFIG_FAT_WRITE is defined.
> This patch also removes compile error when FAT write is enabled and
> compile warning when FAT write is disabled.
>
> Signed-off-by: Donggeun Kim <dg77.kim@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> Changes for v3:
> - use cmd_usage function
> Changes for v2:
> - merge the patch that fixes compile error when enabling FAT write
> - change do_fat_fswrite to be static function
>
> common/cmd_fat.c | 57 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/fat/fat.c | 7 ++++++
> 2 files changed, 64 insertions(+), 0 deletions(-)
This does not apply any more, please rebase against current master and
resubmit.
Sorry.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The years of peak mental activity are undoubtedly between the ages of
four and eighteen. At four we know all the questions, at eighteen all
the answers.
prev parent reply other threads:[~2012-01-05 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 1:34 [U-Boot] [PATCH v3] cmd_fat: add FAT write command Donggeun Kim
2012-01-05 16:23 ` Wolfgang Denk [this message]
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=20120105162354.F41151FD3DA@gemini.denx.de \
--to=wd@denx.de \
--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