From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch] dm355evm NAND support
Date: Mon, 5 Oct 2009 13:26:31 -0700 [thread overview]
Message-ID: <200910051326.31771.david-b@pacbell.net> (raw)
In-Reply-To: <4AC9DDBA.7080004@windriver.com>
On Monday 05 October 2009, Tom wrote:
> In general it is better to break patches that do multiple things into
> multiple patches. When you resubmit, please break this patch into its
> logical parts :
> 1. NAND
> 2. Environment
Hmm, my *original* patch necessarily disabled both
because there was no persistent store to hold the
site-appropriate environment without NAND support.
I was waiting for the 4-bit ECC stuff to merge.
So I don't see those two as being cleanly separable.
> 3. Bootdelay
That makes some sense. Though again, the original
reason for disabling it was the absense of persistent
storage to hold
However, there's evidently been some other stuff
going on since I prepared this patch, so I'll follow
up to Sandeep's post.
- Dave
prev parent reply other threads:[~2009-10-05 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 3:32 [U-Boot] [patch] dm355evm NAND support David Brownell
2009-10-05 11:51 ` Tom
2009-10-05 13:06 ` Paulraj, Sandeep
2009-10-05 20:38 ` David Brownell
2009-10-05 20:47 ` Paulraj, Sandeep
2009-10-05 23:24 ` David Brownell
2009-10-05 20:26 ` David Brownell [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=200910051326.31771.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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