From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH : Fixes and enhancements for NAND flash.
Date: Sat, 26 Jul 2003 23:35:21 +0200 [thread overview]
Message-ID: <20030726213526.54F9AC602D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 24 Jul 2003 18:57:51 CDT." <FD2AC9A020DDD51194710008C7089B200BEE2218@dlee17.itg.ti.com>
Dear Richard,
in message <FD2AC9A020DDD51194710008C7089B200BEE2218@dlee17.itg.ti.com> you wrote:
>
> The following path fixes a few bugs in cmd_nand.c :
> - Fixed null dereference which could result in incorrect ECC values.
> - Added support for devices with no Ready/Busy signal connected.
> - Added OMAP1510 read/write protect handling.
> - Fixed nand.h's ECCPOS. A conflict existed with POS5 and badblock for
> non-JFFS2.
> - Switched default ECC to be JFFS2.
Added so far.
Will push to CVS soon.
> - Added spinning wheel.
Skipped / rejected.
May I please ask you to adhere to the guidlines for coding style?
Please do not add trailing white space, especially not to existing
code.
Please stick with 8 char indentation.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
The man on tops walks a lonely street; the "chain" of command is
often a noose.
next prev parent reply other threads:[~2003-07-26 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 23:57 [U-Boot-Users] PATCH : Fixes and enhancements for NAND flash Woodruff, Richard
2003-07-26 21:35 ` Wolfgang Denk [this message]
2003-07-27 13:20 Woodruff, Richard
2003-07-27 13:38 ` Wolfgang Denk
2003-07-27 16:30 Woodruff, Richard
2003-07-27 17:37 ` Wolfgang Denk
2003-07-27 17:53 ` Robert Schwebel
2003-07-27 18:25 ` Wolfgang Denk
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=20030726213526.54F9AC602D@atlas.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 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.