From: Artem Bityutskiy <dedekind1@gmail.com>
To: "THOMSON, Adam (Adam)" <adam.thomson@alcatel-lucent.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: RE: [PATCH upstream] nand: nand_base: Always initialise oob_poi before writing OOB data
Date: Thu, 23 Jun 2011 11:22:53 +0300 [thread overview]
Message-ID: <1308817376.18119.94.camel@sauron> (raw)
In-Reply-To: <E14CAA9D00C5044EACE0C59FC2A1C7F5059AB4DF22@FRMRSSXCHMBSC1.dc-m.alcatel-lucent.com>
On Wed, 2011-06-22 at 17:40 +0200, THOMSON, Adam (Adam) wrote:
> Adam Thomson Wrote:
> >
> > The original request was for a stable patch, and that would
> > be accepted if I provided a proper tidy fix also. To be fair
> > it was a few weeks ago now that that mail was sent. :-)
> > Anyway, as it turns out the tidy fix was almost identical,
> > and we don't need the memset as far as I can tell from
> > reviewing code and from testing. Will run up your patch today
> > to verify your additional change, but should be fine.
> >
>
> Have tested the updated patch on hardware, and all seems good.
> No problems with OOB corruption, and mtd tests run without failure.
Thank you!
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2011-06-23 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 14:52 [PATCH upstream] nand: nand_base: Always initialise oob_poi before writing OOB data THOMSON, Adam (Adam)
2011-06-22 5:55 ` Artem Bityutskiy
2011-06-22 10:41 ` THOMSON, Adam (Adam)
2011-06-22 10:57 ` Artem Bityutskiy
2011-06-22 11:08 ` THOMSON, Adam (Adam)
2011-06-22 15:40 ` THOMSON, Adam (Adam)
2011-06-23 8:22 ` Artem Bityutskiy [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=1308817376.18119.94.camel@sauron \
--to=dedekind1@gmail.com \
--cc=adam.thomson@alcatel-lucent.com \
--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