From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd_nand.c: Fix 'nand dump' after latest MTD resync
Date: Tue, 28 Feb 2012 14:56:07 -0600 [thread overview]
Message-ID: <4F4D3F67.1000403@freescale.com> (raw)
In-Reply-To: <1330037266-25737-1-git-send-email-trini@ti.com>
On 02/23/2012 04:47 PM, Tom Rini wrote:
> With 2a8e0fc nand_do_read_ops changed in behavior slightly (keeping in sync
> with the kernel which did this change in b64d39d8) such that the OOB data is
> always copied into oobbuf and never appended to datbuf. Within U-Boot only
> the nand_dump function (for the dump nand subcommand) was expecting the OOB
> data to only be appended to datbuf. So we now change nand_dump to not
> malloc extra space, correct the comment about datbuf and OOB data and switch
> the pointer to oobbuf before printing.
>
> Cc: Scott Wood <scottwood@freescale.com>
> Signed-off-by: Tom Rini <trini@ti.com>
> ---
> common/cmd_nand.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
Applied to u-boot-nand-flash
-Scott
prev parent reply other threads:[~2012-02-28 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 22:47 [U-Boot] [PATCH] cmd_nand.c: Fix 'nand dump' after latest MTD resync Tom Rini
2012-02-24 0:55 ` Tom Rini
2012-02-28 20:56 ` Scott Wood [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=4F4D3F67.1000403@freescale.com \
--to=scottwood@freescale.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