All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Paulraj, Sandeep" <s-paulraj@ti.com>
Cc: Troy Kisky <troy.kisky@boundarydevices.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Narnakaje, Snehaprabha" <nsnehaprabha@ti.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"dwmw2@infradead.org" <dwmw2@infradead.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [patch 3/3] mtd-nand: DaVinci: Add 4-bit ECC support for large page NAND chips
Date: Thu, 3 Sep 2009 14:48:42 -0700	[thread overview]
Message-ID: <200909031448.43314.david-b@pacbell.net> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D91E07BD2@dlee01.ent.ti.com>

On Friday 28 August 2009, Paulraj, Sandeep wrote:
> I've already sent the patch to U-Boot and it has been accepted.
> Its in the nand next branch.

Actually at that time it was also in the u-boot-next branch;
and since then (after U-Boot 2009.08 got tagged) it's been
merged into the current U-Boot GIT tree.  :)


> For things to become fully functional i'll need a syncs
> between the various branches of U-Boot. I'll have to enable
> stuff in the DM355 and Dm365 configs    
 
I've got a DM355 config patch; why don't I send that along,
after I test with the latest u-boot and some Linux version
which includes the relevant NAND apatches.  It's been
waiting on that merge, which has now happened.

- Dave

  reply	other threads:[~2009-09-03 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 18:24 [patch 3/3] mtd-nand: DaVinci: Add 4-bit ECC support for large page NAND chips akpm
2009-08-07 19:54 ` Troy Kisky
2009-08-07 19:57   ` Narnakaje, Snehaprabha
2009-08-28  2:08   ` David Brownell
2009-08-28 10:21     ` Paulraj, Sandeep
2009-09-03 21:48       ` David Brownell [this message]
2009-09-03 21:53         ` Paulraj, Sandeep

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=200909031448.43314.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nsnehaprabha@ti.com \
    --cc=s-paulraj@ti.com \
    --cc=tglx@linutronix.de \
    --cc=troy.kisky@boundarydevices.com \
    /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.