From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bhavesh Parekh <bparekh@nvidia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: RE: [PATCH] [MTD:UBI] Missing scrub when there is a bit-flip
Date: Mon, 05 Dec 2011 08:51:17 +0200 [thread overview]
Message-ID: <1323067879.2316.32.camel@koala> (raw)
In-Reply-To: <6F5E0EB93579CE4A99BFB2D6A9D015057D9CA89A59@BGMAIL01.nvidia.com>
On Mon, 2011-12-05 at 11:29 +0530, Bhavesh Parekh wrote:
> Artem,
>
> Currently we have K36 setup with most of the critical ubi fixes in it. Verified that this patch fixes the mentioned issue.
> Also we have K39 tree and I am planning to verify the this issue in that tree as well after porting the change and fixes from the ubi tree.
Thanks. I've added CC to stable in the commit message.
Artem.
prev parent reply other threads:[~2011-12-05 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1322655222-28348-1-git-send-email-bparekh@nvidia.com>
2011-11-30 12:13 ` [PATCH] [MTD:UBI] Missing scrub when there is a bit-flip Bhavesh Parekh
2011-11-30 12:33 ` Artem Bityutskiy
2011-12-04 14:09 ` Artem Bityutskiy
2011-12-05 5:59 ` Bhavesh Parekh
2011-12-05 6:51 ` 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=1323067879.2316.32.camel@koala \
--to=dedekind1@gmail.com \
--cc=bparekh@nvidia.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;
as well as URLs for NNTP newsgroup(s).