From: "Sudhakar Rajashekhara" <sudhakar.raj@ti.com>
To: "'Andrew Morton'" <akpm@linux-foundation.org>
Cc: dwmw2@infradead.org, 'Jon Povey' <Jon.Povey@racelogic.co.uk>,
linux-mtd@lists.infradead.org,
davinci-linux-open-source@linux.davincidsp.com
Subject: RE: [PATCH v2] mtd-nand: davinci: correct 4-bit error correction
Date: Fri, 23 Jul 2010 15:19:49 +0530 [thread overview]
Message-ID: <051701cb2a4c$6456ead0$2d04c070$@raj@ti.com> (raw)
In-Reply-To: <20100721150058.dfb4ef06.akpm@linux-foundation.org>
Hi,
On Thu, Jul 22, 2010 at 03:30:58, Andrew Morton wrote:
> On Thu, 15 Jul 2010 17:33:03 +0530
> "Sudhakar Rajashekhara" <sudhakar.raj@ti.com> wrote:
>
> > On Thu, Jul 15, 2010 at 17:11:32, Sudhakar Rajashekhara wrote:
> > > Hi,
> > >
> > > On Thu, Jul 15, 2010 at 16:31:19, Jon Povey wrote:
> > > > Sudhakar Rajashekhara wrote:
> > > > > On TI's DA830/OMAP-L137, DA850/OMAP-L138 and DM365, after setting the
> > > > > 4BITECC_ADD_CALC_START bit in the NAND Flash control register to 1 and
> > > > > before waiting for the NAND Flash status register to be equal to 1, 2
> > > > > or 3, we have to wait till the ECC HW goes to correction state.
> > > > > Without this wait, ECC correction calculations will not be proper.
> > > > >
> > > > > This has been tested on DA830/OMAP-L137, DA850/OMAP-L138, DM355 and
> > > > > DM365 EVMs.
> > > > >
> > > > > Signed-off-by: Sudhakar Rajashekhara <sudhakar.raj@ti.com>
> > > > > Acked-by: Sneha Narnakaje <nsnehaprabha@ti.com>
> > > > > Cc: David Woodhouse <dwmw2@infradead.org>
> > > > > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > > >
> > > > Have these people acked and signed off this new version of the patch?
> > > >
> > >
> > > No. Andrew Morton has not signed off this version. I'll remove
> > > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > >
> >
> > Andrew Morton had signed off an earlier version of this patch and
> > it was present in -mm tree for a long time. He has not yet commented
> > on v2 version of this patch. But I thought I can carry forward the
> > Sign-offs from previous version to the next version. What's the common
> > practice?
> >
>
>
> I've lost the plot on this patch and I think I'll drop my copy. Please
> update and resend, cc'ing everyone.
>
> I've been sitting on this thing since November last year! It fixes a
> bug! Where the heck are the MTD maintainers and why aren't they
> running around with hair on fire getting this thing finalised and
> merged?!?!
>
I got an e-mail from Artem Bityutskiy(dedekind1@gmail.com) saying that
he has pushed this patch to his l2-mtd-2.6/master tree. May be it will
get to upstream from there.
Thanks,
Sudhakar
next prev parent reply other threads:[~2010-07-23 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 5:10 [PATCH v2] mtd-nand: davinci: correct 4-bit error correction Sudhakar Rajashekhara
2010-07-15 11:01 ` Jon Povey
2010-07-15 11:41 ` Sudhakar Rajashekhara
2010-07-15 12:03 ` Sudhakar Rajashekhara
2010-07-21 22:00 ` Andrew Morton
2010-07-23 9:49 ` Sudhakar Rajashekhara [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-10 9:36 [PATCH v2] mtd-nand: davinci: Correct " Sudhakar Rajashekhara
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='051701cb2a4c$6456ead0$2d04c070$@raj@ti.com' \
--to=sudhakar.raj@ti.com \
--cc=Jon.Povey@racelogic.co.uk \
--cc=akpm@linux-foundation.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).